[ http://jira.codehaus.org/browse/MOJO-301?page=comments#action_59294 ]
Oliver Siegmar commented on MOJO-301: ------------------------------------- > Ok, version 1.4.2 fixes the path issue for your tools.jar. No, unfortunately not. I still have to include the system-dependency otherwise the same error happens (with 1.4.2). The strange thing is, that the classpath shown in the error message includes tools.jar (in the right path). > 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. The class is part of the project itself and gets compiled. I'm really stuck on that, it is a really simple .tag file and the error message doesn't show up the classpath used. >> BTW: Is there a configuration option that removes all successfully compiled >> jsp files from target? > mvn clean :-)) No...I mean the JSP files in the .war > 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
