Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Duplicate
-
Affects Version/s: 2.4, 2.5.1
-
Fix Version/s: 2.6
-
Component/s: dependency-management
-
Labels:None
-
Environment:java 6.0.27, maven 3.0.3
-
Number of attachments :
Description
In my pom I have
<dependencyManagement> <dependencies> <dependency> <groupId>cz.komix.maven</groupId> <artifactId>spring-security-deps</artifactId> <type>pom</type> <version>3.0.5</version> <scope>import</scope> </dependency> </dependencies> </dependencyManagement>
cz.komix.maven:spring-security-deps:3.0.5 is simple pom with dependencyManagement section with spring artifacts versions
Running mvn site with <report>dependency-management</report> cause version update checks for every of those spring artifact. Is there any reason for such update check?
It is made for every artifact in dependency-management section, even for those that is are not even used as dependency! It should be possible to turn it off like <dependencyDetailsEnabled>false</dependencyDetailsEnabled> at least.
Same problem here!
The logfile and console of our daily site build via Jenkis are totally flooded with stacktraces because SNAPSHOT-versions are not found (for obvious reasons).