[
http://jira.codehaus.org/browse/MJSPC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98838
]
Jason Dillon commented on MJSPC-11:
-----------------------------------
Until the docs are updated, looks at the integration tests for how to use:
*
http://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/jspc/jspc-maven-plugin/src/it/jspc-1/
> Getting more control on what version of tomcat is used
> ------------------------------------------------------
>
> Key: MJSPC-11
> URL: http://jira.codehaus.org/browse/MJSPC-11
> Project: Maven 2.x JSPC Plugin
> Issue Type: Wish
> Affects Versions: 1.4.7
> Reporter: Grégory Joseph
> Assignee: Jason Dillon
> Fix For: 2.0
>
>
> I can't manage to force the jspc plugin to use tomcat5.5 (or 5.0). I can't
> just redefine the tomcat dependency in my <plugin> declaration, since tomcat5
> artifacts are in a different groupId, both end up on the classpath.
> I have no suggestion on how to implement this, but I'd really like to be able
> to get more control on this.
> One way could maybe be to release several versions of the plugin, shipped
> with different dependencies ?
> Or, more annoying to users, remove the deps to tomcat altogether, so users
> would have to declare whichever they want.
> (the initial reason why I wanted to do this is because we ship our product
> with tomcat5, but also because I had errors that seemed to say I needed
> servlet2.5 and jsp2.1... after lots of experimenting today, it now seems to
> work for some odd reason, so I can live with it...)
--
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
