Dependency scope of "tomcat" needed for addContextWarDependencies to work in
run/run-war goals.
-----------------------------------------------------------------------------------------------
Key: MTOMCAT-75
URL: http://jira.codehaus.org/browse/MTOMCAT-75
Project: Maven 2.x Tomcat Plugin
Issue Type: Improvement
Affects Versions: 1.1
Environment: Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400)
Java version: 1.6.0_22
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x" version: "10.5.8" arch: "x86_64" Family: "mac"
Reporter: Ryan Connolly
The feature to deploy dependency wars to embedded containers created with
tomcat:run and tomcat:run-war depend upon a war dependency scope being defined
as "tomcat". It would seem a much cleaner to allow the configuration of such
war dependencies in the plugin dependencies using a valid dependency scope.
Log Output:
[WARNING] Some problems were encountered while building the effective model for
com.rynam0:tomcat-maven-plugin-test:war:1.0-SNAPSHOT
[WARNING] 'dependencies.dependency.scope' for com.rynam0:simple-portal-war:war
must be one of [provided, compile, runtime, test, system] but is 'tomcat'. @
line 22, column 14
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
--
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
