Maven 2.x Project Info Reports Plugin

dependency-management is checking for SNAPSHOT updates

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical 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 :
    0

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.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MPIR-255 DependencyManagement report reads every artifact from repository

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Bug - A problem which impairs or prevents the functions of the product. MPIR-216 Report on dependency-management throws Exceptions using version range for dependency

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Falko Modler added a comment -

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).

Show
Falko Modler added a comment - 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).
Kristian Rosenvold made changes -
Field Original Value New Value
Link This issue is duplicated by MPIR-255 [ MPIR-255 ]
Kristian Rosenvold made changes -
Status Open [ 1 ] Closed [ 6 ]
Assignee Herve Boutemy [ hboutemy ]
Resolution Duplicate [ 3 ]
Kristian Rosenvold made changes -
Fix Version/s 2.6 [ 18761 ]
Herve Boutemy made changes -
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. 		In my pom I have
{code:xml} <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>{code}

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.
Herve Boutemy made changes -
Affects Version/s 2.5.1 [ 18715 ]
Affects Version/s 2.4 [ 17000 ]
Priority Major [ 3 ] Critical [ 2 ]
Herve Boutemy made changes -
Link This issue is related to MPIR-216 [ MPIR-216 ]

People

  • Assignee:
    Herve Boutemy
    Reporter:
    Martin Vanek
Vote (5)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: