JSP precompilation breaks next build
------------------------------------
Key: MAVEN-26
URL: http://thecla.homeftp.net:8380/jira/browse/MAVEN-26
Project: Maven Plugins
Type: Bug
Components: APP
Environment: all
Reporter: Thomas Schapitz
Assigned to: Chad Brandon
Priority: Minor
Triggering JSP-precompilation for JSPs generated by the bpm4struts cartidge
works fine on a clean directory.
But when executing the goal 'web' a second time, the java sources that jasper
shelled
out on the first execution get caught by the java:compile goal meant for the
original
sources.
This breaks the build, because this comile step isn't configured to find the
org.andromda.taglib.* packages.
Current workarounds:
- disable JSP precompilation
- clean the directory before building the web app.
Solution: jasper should keep the generated sources out of sight of the
java:compile goal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://thecla.homeftp.net:8380/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel
