Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.3.1
-
Fix Version/s: 1.3.4
-
Component/s: Project infrastructure
-
Labels:None
-
Environment:irrelevant
-
Testcase included:yes
Description
javadoc and java source JARs are being packaged into the WAR. This can be seen with a dependency such as:
dependencies {
compile("net.sf.ehcache:ehcache-web:2.0.0")
}
You will find
WEB-INF\lib\ehcache-web-2.0.0-javadoc.jar
WEB-INF\lib\ehcache-web-2.0.0-javadoc.jar
in your WAR.
'provided' scoped dependencies are also being included in the WAR.
One example I have found is from 'http://download.java.net/maven/2/' repository:
dependencies {
compile('com.sun.jersey:jersey-server:1.1.5.1')
}
That artifact's POM declares dependencies like:
<dependency>
<groupId>com.sun.grizzly</groupId>
<artifactId>grizzly-servlet-webserver</artifactId>
<version>1.9.8</version>
<scope>provided</scope>
</dependency>
You will find the grizzly JARs in your WAR.
I've been debugging the issue as best I can. There appears to be a problem in the IvyDependencyManager.resolveDependencies(String conf) method. I notice that when the resolveEngine attempts to resolve the descriptor the options appear to be ineffective. IE, if conf is 'runtime' the resolve report will still contain test artifacts etc.