[ http://jira.codehaus.org/browse/MOJO-301?page=comments#action_59160 ]
Jeff Genender commented on MOJO-301: ------------------------------------ You need to add the jasper-runtime dependency to your pom. You have gotten past the jspc plugin and you are now in your regular compile goal. I think I fixed the system dependency issue. I put up version 1.4.1 of the plugin and it will add the tools.jar (or classes.jar on Mac) to the classpath automatically. Please give this a try and see if this takes care of the issues. > 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 > > > 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
