[ http://jira.codehaus.org/browse/MOJO-301?page=comments#action_59397 ]
Oliver Siegmar commented on MOJO-301: ------------------------------------- Thanks for your help, Jeff. The tools.jar problem is fixed in trunk. I've found another dependency/classloader issue which I've filed as MOJO-312. About the chicken/egg problem - building a seperate types-jar is a bit oversized in simple cases. How to "create a compile execution for javac that will run before the jspc plugin"? I think, that the correct build lifecycle should be "build, jspc, build" - this would be the same behaviour as without jspc - "maven build, j2ee container generates java code, j2ee container builds". I have another issue found and will create another ticket, so that this can be closed now, I guess. Maybe you could add a ticket about the chicken/egg problem - you can better describe what the problem is and how it may be resolved. > jspc-maven-plugin doesn't seem to work at all > --------------------------------------------- > > Key: MOJO-301 > URL: http://jira.codehaus.org/browse/MOJO-301 > Project: Mojo > Type: Bug > Reporter: Oliver Siegmar > Attachments: maven-jspc-example.tar.gz > > > Sorry for that stupid summarization - I don't know how to summarize this > problem. > When calling 'mvn package' I see this on my shell: > [INFO] jspc args: [-uriroot, /XXX/src/main/webapp, -d, > /XXX/target/jsp-source, -s, -l, -webinc, /XXX/target/web-fragment.xml, -p, > jsp] > org.apache.jasper.JasperException: The absolute uri: > http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the > jar files deployed with this application > My fault? -- 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
