maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MDEP-213) resolve dependencyManagement section with option to fail the build
Date Tue, 12 Jan 2016 20:12:42 GMT

     [ https://issues.apache.org/jira/browse/MDEP-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov closed MDEP-213.
-------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still persists, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> resolve dependencyManagement section with option to fail the build
> ------------------------------------------------------------------
>
>                 Key: MDEP-213
>                 URL: https://issues.apache.org/jira/browse/MDEP-213
>             Project: Maven Dependency Plugin
>          Issue Type: New Feature
>          Components: resolve
>    Affects Versions: 2.0
>            Reporter: Jim Sellers
>
> When using the dependencyManagement section of a pom of type "pom" to create a bill of
materials, it's currently possible to specify an invalid version.  eg:
> {code:xml}
> 	<dependencyManagement>
> 		<dependencies>
> 			<dependency>
> 				<groupId>commons-logging</groupId>
> 				<artifactId>commons-logging</artifactId>
> 				<version>9.9</version>
> 			</dependency>
> 		</dependencies>
> 	</dependencyManagement>
> {code} 
> It would be really useful for these types of pom's to be able to force all the dependencies
to be resolved when running something like "install" and have that fail the build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message