[
http://jira.codehaus.org/browse/MOJO-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87375
]
Parolini Antonio commented on MOJO-307:
---------------------------------------
I thought it would be possible to put the jasper 4.1.31 api in the dependencies
of the plugin inside of the webapp pom, and use profiles to swap between tomcat
4 or 5 like this:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jspc-maven-plugin</artifactId>
<dependencies>
<dependency>
<groupId>tomcat</groupId>
<artifactId>jasper-runtime</artifactId>
<version>4.1.31</version>
</dependency>
<dependency>
<groupId>tomcat</groupId>
<artifactId>jasper-compiler</artifactId>
<version>4.1.31</version>
</dependency>
</dependencies>
I tried but I doesn't seem to work: java.lang.NoClassDefFoundError:
org/apache/jasper/logging/Logger
Any ideas why dosen't work ?
> JSPC - need version that compiles for servlet 2.3 and jsp 1.2 spec using
> jasper 4.1.31
> --------------------------------------------------------------------------------------
>
> Key: MOJO-307
> URL: http://jira.codehaus.org/browse/MOJO-307
> Project: Mojo
> Issue Type: Improvement
> Components: jspc
> Reporter: Tomislav Stojcevich
> Priority: Minor
>
> There are stile many web applications deployed using the 2.3 servlet spec,
> thus jsp compiles with that spec are needed.
> A simple change to the POM (changing the servlet/jsp versions and the jasper
> compiler version) should do the trick.
> The problem is that 2 versions would need to be deployed as a seperate plugin
> because of the pom differences.
> Perhaps version them seperately and include the spec (2.3/1.2 or 2.4/2.0) as
> part of the version number or maybe include the version number as part of the
> name?
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
