Maven 2 & 3

Unrecognised association "exclude" in pom parsing <resource><directory><excludes> in 2.0.10-RC10

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Not A Bug
  • Affects Version/s: 2.0.10
  • Fix Version/s: None
  • Component/s: POM
  • Labels:
    None
  • Environment:
    XP SP3, Java 1.5.0_12-b04, Maven 2.0.10-RC10 2/1/09.
  • Complexity:
    Intermediate
  • Number of attachments :
    4

Description

Fails in Maven 2.0.10-RC10, works in 2.0.8 and 2.0.9. pom.xml containing the following:
<resources>
<resource>
<directory>src/java</directory>
<excludes>
<exclude>*/.java</exclude>
</excludes>
</resource>

Fails with:
org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. Reason: Unrecognised association: 'excludes' (position: START_TAG seen ...<excludes>\
<excludes>... @138:31) for project unknown:andromda-metafacades-uml at C:\workspaces\A34\andromda34\metafacades\uml\pom.xml

Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error reading POM. Reason: Unrecognised association: 'excludes' (position: START_TAG seen ...<excludes>\r\n <excludes>... @138:31) for project unknown:andromda-metafacades-uml at C:\workspaces\A34\andromda34\metafacades\uml\pom.xml
at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1591)

Not sure if this is related to http://jira.codehaus.org/browse/MNG-3680

pom.xml and mvn -X output from 2.0.9 and 2.0.10 attached. Pom file is from AndroMDA: http://team.andromda.org/docs/source-repository.html under directory metafacades\uml.

  1. Text File
    209Debug.log
    02/Feb/09 5:28 PM
    192 kB
    Bob Fields
  2. Text File
    210Debug.log
    02/Feb/09 5:28 PM
    4 kB
    Bob Fields
  3. XML File
    pom.xml
    03/Feb/09 8:22 AM
    25 kB
    Bob Fields
  4. XML File
    pom.xml
    02/Feb/09 5:28 PM
    7 kB
    Bob Fields

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-3645 Maven doesn't do strict model validation for POMs in the current reactor

  • 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
Bob Fields added a comment -

Oops, I meant to say 2.0.10-RC8, built on 2/1/09, downloaded from http://people.apache.org/~brianf/staging-repository2/org/apache/maven/apache-maven/2.0.10-RC8.

Show
Bob Fields added a comment - Oops, I meant to say 2.0.10-RC8, built on 2/1/09, downloaded from http://people.apache.org/~brianf/staging-repository2/org/apache/maven/apache-maven/2.0.10-RC8 .
Hide
Permalink
Benjamin Bentmann added a comment -

Bob, could you also attach the parent POM of the one you already provided, i.e. andromda-uml-metafacades:3.4.1-SNAPSHOT. In CVS, I only found 3.4-SNAPSHOT which apparently isn't the same.

Show
Benjamin Bentmann added a comment - Bob, could you also attach the parent POM of the one you already provided, i.e. andromda-uml-metafacades:3.4.1-SNAPSHOT. In CVS, I only found 3.4-SNAPSHOT which apparently isn't the same.
Hide
Permalink
Bob Fields added a comment -

All I did was change 3.4-SNAPSHOT to 3.4.1-SNAPSHOT locally, in order to prevent my custom local extensions from being overwritten automatically by the AndroMDA 3.4-SNAPSHOT downloaded version. I would think you would see the same problem from the pom.xml downloaded from the web site, but I haven't tried yet, I can try it today.

Attached top level parent pom.xml.

Show
Bob Fields added a comment - All I did was change 3.4-SNAPSHOT to 3.4.1-SNAPSHOT locally, in order to prevent my custom local extensions from being overwritten automatically by the AndroMDA 3.4-SNAPSHOT downloaded version. I would think you would see the same problem from the pom.xml downloaded from the web site, but I haven't tried yet, I can try it today. Attached top level parent pom.xml.
Hide
Permalink
Benjamin Bentmann added a comment -

From the immediate parent POM of the POM you provided first:

<testResource>
  <directory>src/test/java</directory>
  <excludes>
    <excludes>**/*.java</excludes>  <!-- Note the plural here, it should however be <exclude> -->
  </excludes>
</testResource>

i.e. the POM is indeed invalid, cf. the XSD.

Show
Benjamin Bentmann added a comment - From the immediate parent POM of the POM you provided first: <testResource> <directory> src/test/java </directory> <excludes> <excludes> **/*.java </excludes> <!-- Note the plural here, it should however be <exclude> --> </excludes> </testResource> i.e. the POM is indeed invalid, cf. the XSD .
Hide
Permalink
Bob Fields added a comment -

Thank you for pointing that out, I'll fix the file on AndroMDA. I guess it was just a simple mistake from the previous developers that I didn't notice. A warning in the previous maven version would have been nice, I guess it just ignored the configuration information it didn't understand.

This issue can be closed.

Show
Bob Fields added a comment - Thank you for pointing that out, I'll fix the file on AndroMDA. I guess it was just a simple mistake from the previous developers that I didn't notice. A warning in the previous maven version would have been nice, I guess it just ignored the configuration information it didn't understand. This issue can be closed.

People

  • Assignee:
    Benjamin Bentmann
    Reporter:
    Bob Fields
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: