[MTOMCAT-75] Dependency scope of "tomcat" needed for addContextWarDependencies to work in run/run-war goals.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 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"

• Assignee: Olivier Lamy
• Reporter: Ryan Connolly
• Created: 13/Jan/11 07:37
• Updated: 04/Nov/13 04:13
• Resolved: 04/Nov/13 04:13

Description

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]

Issue Links

• duplicates: MTOMCAT-74 Deploy war type plugin dependencies with tomcat:run