Maven 2.x Castor Plugin

Castor test cases are not reactor friendly. Cannot build from mojo root.

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

When running the build from the top, the castor tests fail with the following. They appear to be looking for mapping.xml from the root of the build, not of the artifact's project.

[info] Processing /data/users/bravo/projects/open source/codehaus-maven/trunk/mojo/src/test/resources/mapping.xml
[info] XML Schema file "/data/users/bravo/projects/open source/codehaus-maven/trunk/mojo/src/test/resources/mapping.xml" not found .
[info] Processing /data/users/bravo/projects/open source/codehaus-maven/trunk/mojo/src/test/resources/mapping.xml
[info] XML Schema file "/data/users/bravo/projects/open source/codehaus-maven/trunk/mojo/src/test/resources/mapping.xml" not found .
[info] Processing /data/users/bravo/projects/open source/codehaus-maven/trunk/mojo/src/test/resources/mapping.xml
[info] XML Schema file "/data/users/bravo/projects/open source/codehaus-maven/trunk/mojo/src/test/resources/mapping.xml" not found .
[info] Nothing to process - all xsds are up to date
[surefire] Running org.apache.maven.plugins.castor.CodeGeneratorMojoTest
[surefire] Tests run: 11, Failures: 0, Errors: 4, Time elapsed: 0 sec <<<<<<<< FAILURE !!

Activity

Hide
Permalink
Matt Brozowski added a comment -

This had been reported previously (MOJO-134) with the identical diagnosis. The code was then fixed near the end of November.

I just did a clean checkout of the entire mojo repositoy and did mvn package from the parent project. The castor project compiled, tested and packaged just fine. (Unfortunately it breaks in the same place it broke when I worked on this last time. In Jalopy. See MOJO-163)

Is it possible you failed to update the castor plugin before building?

Reopen this if not and I am missing something

Show
Matt Brozowski added a comment - This had been reported previously (MOJO-134) with the identical diagnosis. The code was then fixed near the end of November. I just did a clean checkout of the entire mojo repositoy and did mvn package from the parent project. The castor project compiled, tested and packaged just fine. (Unfortunately it breaks in the same place it broke when I worked on this last time. In Jalopy. See MOJO-163 ) Is it possible you failed to update the castor plugin before building? Reopen this if not and I am missing something

People

  • Assignee:
    Matt Brozowski
    Reporter:
    Corridor Software Developer
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: