[MWAR-101] Scoped dependencies are not handled correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1-alpha-1
• Fix Version/s: 2.1-alpha-2
• Environment: maven-2.0.6
• Assignee: Stephane Nicoll
• Reporter: Jörg Hohwiller
• Created: 08/May/07 15:19
• Updated: 07/Apr/15 18:37
• Resolved: 28/Oct/07 05:03

Description

I have a maven module with packaging war that has various dependencies. When the webapp is build by the war-plugin, some dependencies are NOT copied to the WEB-INF/lib directory of the webapp.
This seems to have something to do with the fact that in this case I have the same dependency twice once as a regular dependency and another time with classifier "sources". This is necessary since I am using the Google-Web-Toolkit that needs the sources of dependent client modules.
So I have such dependecies in my POM:
<dependency>
<groupId>foo.bar</groupId>
<artifactId>web-client</artifactId>
<version>1.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>foo.bar</groupId>
<artifactId>web-client</artifactId>
<version>1.0</version>
<scope>compile</scope>
<classifier>sources</classifier>
</dependency>

This works fine for compilation where the GWT reads the sources from the classpath.
However there is no "web-client-*.jar" in WEB-INF/lib but one "foo.bar-web-client-1.0.jar" that holds the content
of the "web-client-1.0-sources.jar".
I do not know what goes wrong here, but I looks that the war-plugin detects some kind of clush for this "duplicate" depdency and makes some magic that seems wrong here...