On 4/27/07, Gregory Kick <[EMAIL PROTECTED]> wrote:
I think that instead of using optional, you have been meaning to use <scope>provided</scope>. This would indicate that the jars are necessary, but won't include them in your war because it is assumed that it will be provided by the container, or in your case, the ear.
Nope. Cf last part of http://maven.apache.org/plugins/maven-war-plugin/examples/war-manifest-guide.html
As far as your testing, you could setup a container that has those artifacts as part of the common libraries and deploy to that. For example, if you're using the jetty plugin, http://ramblingabout.wordpress.com/2007/01/12/jsf-on-jetty-and-maven/ says that you can just add them as dependencies for the plugin. I haven't tried it, but it seems reasonable.
That's not satisfying. I will have to put this environment each time my dependencies are changed. That's just pushing the problem away. Cheers, Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
