[
http://jira.codehaus.org/browse/MOJO-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95830
]
jake pezaro commented on MOJO-653:
----------------------------------
this problem is caused by how maven creates classpaths in a multi-module build.
for dependent jars (not compiled during the build) the classpath includes the
path to the jar, but in included projects maven includes the project's build
directory (usually something like ${basedir}/target/classes} ).
jspc (specifically the org.apache.jasper.compiler.TldLocationsCache.scanJars()
method) ignores all entries on the classpath that are not jar files.
the reason that installing the sub-projects individually works is that the
dependencies are all represented as jar files by maven.
> classpath incorrect with mvn test in reactor build
> --------------------------------------------------
>
> Key: MOJO-653
> URL: http://jira.codehaus.org/browse/MOJO-653
> Project: Mojo
> Issue Type: Bug
> Components: jspc
> Reporter: Stefan Seidel
> Priority: Minor
> Attachments: jsp-c.zip, jsp-c.zip
>
>
> When using custom TLDs with the jsp-compiler plugin in a reactored build, the
> target/classes path is being added to the classpath for the jsp-c plugin
> instead of the path to the .jar file. Therefore the build fails not finding
> the URI for the defined TLDs. See attached sample project. When doing mvn
> install, everything works, also when doing mvn process-test-resources for
> each single module. When starting mvn test on the parent pom, the build fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
