Maven 2.x Assembly Plugin

Assembly Descriptor Schemas (XSD) have wrong targetNamespace

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 2.2-beta-2
  • Fix Version/s: 2.2-beta-2
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

There are two versions of Assembly XSDs on the website:
http://maven.apache.org/plugins/maven-assembly-plugin/

Both define a targetNamespace "http://maven.apache.org/POM/4.0.0" which is wrong because those XSDs define the Schema for the Assembly Descriptor and not the POM.

Proposed fix for assembly-1.0.0.xsd:
Change targetNamespace and xmlns to something like "http://maven.apache.org/Assembly/1.0.0"

Proposed fix for assembly-1.1.0-SNAPSHOT.xsd:
Change targetNamespace and xmlns to something like "http://maven.apache.org/Assembly/1.1.0"

Regards,
Manfred

Issue Links

relates to

Improvement - An improvement or enhancement to an existing feature or task. MNG-3224 Maven XML schemes are not usable in XML catalogs

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Manfred Geiler added a comment -

PING

Just searched, but have no idea, where those XSDs are located in the SVN repo.
If someone points me to them I can provide a patch.

Regards,
Manfred

Show
Manfred Geiler added a comment - PING Just searched, but have no idea, where those XSDs are located in the SVN repo. If someone points me to them I can provide a patch. Regards, Manfred
Hide
Permalink
Dennis Lundberg added a comment -

The xsd file is generated by Modello. The source file that is fed into Modello can be found here:
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/main/mdo/descriptor.mdo

Show
Dennis Lundberg added a comment - The xsd file is generated by Modello. The source file that is fed into Modello can be found here: https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/main/mdo/descriptor.mdo
Hide
Permalink
Manfred Geiler added a comment -

Hmm, no idea how modello generates the "targetNamespace".
Is it derived from the rootElement class definition?
Any modello expert here?
I would guess that the following "patch" could do the job:

<class rootElement="true" xml.tagName="assembly">
<name>Assembly</name>
<description>
<![CDATA[
An assembly defines a collection of files usually distributed in an
archive format such as zip, tar, or tar.gz that is generated from a
project. For example, a project could produce a ZIP assembly which
contains a project's JAR artifact in the root directory, the
runtime dependencies in a lib/ directory, and a shell script to launch
a stand-alone application.
]]>
</description>

  • <version>1.0.0+</version>
    + <version>1.1.0+</version>
    <fields>

But perhaps that could have the sideeffect that 1.0.0 assemblies could not longer be read?

Show
Manfred Geiler added a comment - Hmm, no idea how modello generates the "targetNamespace". Is it derived from the rootElement class definition? Any modello expert here? I would guess that the following "patch" could do the job: <class rootElement="true" xml.tagName="assembly"> <name>Assembly</name> <description> <![CDATA[ An assembly defines a collection of files usually distributed in an archive format such as zip, tar, or tar.gz that is generated from a project. For example, a project could produce a ZIP assembly which contains a project's JAR artifact in the root directory, the runtime dependencies in a lib/ directory, and a shell script to launch a stand-alone application. ]]> </description> <version>1.0.0+</version> + <version>1.1.0+</version> <fields> But perhaps that could have the sideeffect that 1.0.0 assemblies could not longer be read?
Hide
Permalink
John Casey added a comment -

this is resolved for the 1.1.0 target namespace (for 2.2-beta-2), but needs a more permanent solution to support automatic filtering of the target version into the mdo files...

Show
John Casey added a comment - this is resolved for the 1.1.0 target namespace (for 2.2-beta-2), but needs a more permanent solution to support automatic filtering of the target version into the mdo files...
Hide
Permalink
Olve Sæther Hansen added a comment -

I just ran into this problem, and I cant see that this is fixed for the 1.1.0..
http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd (as in the actual URL) still points to

targetNamespace="http://maven.apache.org/POM/4.0.0" xmlns="http://maven.apache.org/POM/4.0.0"

Will it be fixed only in the final release, and not in the snapshot?

Show
Olve Sæther Hansen added a comment - I just ran into this problem, and I cant see that this is fixed for the 1.1.0.. http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd (as in the actual URL) still points to targetNamespace="http://maven.apache.org/POM/4.0.0" xmlns="http://maven.apache.org/POM/4.0.0" Will it be fixed only in the final release, and not in the snapshot?

People

  • Assignee:
    John Casey
    Reporter:
    Manfred Geiler
Vote (0)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: