[
https://jira.codehaus.org/browse/MPIR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291253#comment-291253
]
Falko Modler commented on MPIR-233:
-----------------------------------
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).
> dependency-management is checking for SNAPSHOT updates
> ------------------------------------------------------
>
> Key: MPIR-233
> URL: https://jira.codehaus.org/browse/MPIR-233
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-management
> Environment: java 6.0.27, maven 3.0.3
> Reporter: Martin Vanek
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
