[ http://jira.codehaus.org/browse/MOJO-301?page=comments#action_59251 ]
Jeff Genender commented on MOJO-301: ------------------------------------ Ok, version 1.4.2 fixes the path issue for your tools.jar. The JasperException is usually attributed to your tld and jars being available to the classpath (dependency). Be sure your (a.self.defined.attribute.class) is available via your dependencies. I have updated to the 5.5.15 version of jasper compiler and it may help, but I think this is a classpath issue. >> BTW: Is there a configuration option that removes all successfully compiled >> jsp files from target? mvn clean > 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
