[#MULE-1559] Publish updated Mule 1.4 DTDs at http://mule.mulesource.org/dtds/mule-configuration.dtd

Details

Type: Task
Status: Closed
Priority: Critical
Resolution: Fixed
Affects Version/s: 1.4.0
Fix Version/s: 1.4.0
Component/s: Core: Configuration, Tools
Labels:
None

Similar Issues:
~~MULE-1710~~ Publish updated Mule 1.4.1 DTDs at http://mule.mulesource.org/dtds/mule-configuration.dtd
~~MULE-778~~ Mule configuration DTDs gone from web site
~~MULE-293~~ MuleXmlConfigurationBuilder does not load mule-spring-configuration.dtd if there is no internet connection
~~MULE-3152~~ Oracle Database not closing
~~MULE-51~~ Update Mule dtd and upload it to www.cubis.co.uk/dtds/
~~MULE-901~~ Nightly full distribution snapshots to be published at http://snapshots.dist.codehaus.org/mule/
~~MULE-2826~~ Deploy updated DTDs as part of release
~~MULE-1795~~ Publish Mule JavaDocs for multiple releases
~~MULE-1688~~ VM Transport slow in 1.4 when queueEvents = "true"
~~MULE-1706~~ Publish Mule 2.0 schemas

Description

Use the versions from the mule-1.4 branch

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Holger Hoffstaette added a comment - 09/Apr/07 12:25 PM

The unversioned DTD URL is quite a problem. Is there any easy/quick/simple way we can have versioned DTDs? I know they are going out of style with 2.0 but then again they will still be with us for a long time. We cannot retroactively fix <1.4 but just publishing the latest at the same location seems somehow wrong and confusing for people using older releases. Any ideas? Would adding the major version number to the filename solve this?

Show

Holger Hoffstaette added a comment - 09/Apr/07 12:25 PM The unversioned DTD URL is quite a problem. Is there any easy/quick/simple way we can have versioned DTDs? I know they are going out of style with 2.0 but then again they will still be with us for a long time. We cannot retroactively fix <1.4 but just publishing the latest at the same location seems somehow wrong and confusing for people using older releases. Any ideas? Would adding the major version number to the filename solve this?

Hide

Permalink

Andrew Perepelytsya added a comment - 09/Apr/07 12:30 PM

I'm fine with having a 1.4 suffix in the name (and corresponding 2.0 one later), and have them published in the same folder. The only downside is that all examples in the distribution (and later - Confluence) have to be updated.

If we go that route, we should be able to update the distribution by 1.4 final.

Show

Andrew Perepelytsya added a comment - 09/Apr/07 12:30 PM I'm fine with having a 1.4 suffix in the name (and corresponding 2.0 one later), and have them published in the same folder. The only downside is that all examples in the distribution (and later - Confluence) have to be updated. If we go that route, we should be able to update the distribution by 1.4 final.

Hide

Permalink

Ross Mason added a comment - 10/Apr/07 02:22 AM

As part of deployment, it would be good if the old DTD was renamed to mule-configuration-1.3.3.dtd and the new one uploaded so that folks can still reference back versions explicitly if needed.

Show

Ross Mason added a comment - 10/Apr/07 02:22 AM As part of deployment, it would be good if the old DTD was renamed to mule-configuration-1.3.3.dtd and the new one uploaded so that folks can still reference back versions explicitly if needed.

Hide

Permalink

Ross Mason added a comment - 10/Apr/07 05:48 AM

I think we should keep mule-configuration.dtd as the most recent on the server so that we do go breaking everyone's configuration. But I do think we should be attaching the major version to the name of the dtd. Since, 1.4 is likely to be the last 1.x major release I don't think we should rock the boat too much. The schemas are versioned by their namespace in Mule 2.0.

Show

Ross Mason added a comment - 10/Apr/07 05:48 AM I think we should keep mule-configuration.dtd as the most recent on the server so that we do go breaking everyone's configuration. But I do think we should be attaching the major version to the name of the dtd. Since, 1.4 is likely to be the last 1.x major release I don't think we should rock the boat too much. The schemas are versioned by their namespace in Mule 2.0.

People

Assignee:

Dirk Olmes

Reporter:

Andrew Perepelytsya

Vote (0)

Watch (0)

Dates

Created:

06/Apr/07 01:30 PM

Updated:

17/Apr/07 03:53 AM

Resolved:

17/Apr/07 03:53 AM