Hi Benson,
On 10/11/15 11:39 PM, Benson Margulies wrote:
Hey, I just assume that the JIRAs are correct. What component do you
think it should be?
sorry i couldn't read...So the question is: Is this completely done or
not? Based on the jira it is not and neither based on the svn history...
So this should be moved forward to a new release of the component...
Kind regards
Karl Heinz Marbaise
On Sun, Oct 11, 2015 at 4:51 PM, Karl Heinz Marbaise <[email protected]> wrote:
Hi,
If i take a look into JIRA there are 4 issues in 3.0 release...
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12331490
is MSHARED-420 wrongly assigned to maven-dependency-tree 3.0, cause it is
not part of the release nor it is it ready ?
Kind regards
Karl Heinz Marbaise
On 10/10/15 9:04 PM, Benson Margulies wrote:
The Maven team is pleased to announce the release of the Apache Maven
Dependency Tree, version 3.0
A tree-based API for resolution of Maven project dependencies
http://maven.apache.org/shared/maven-dependency-tree/
You should specify the version in your project's dependency configuration:
<dependency>
<groupId>org.apache.maven.shared</groupId>
<artifactId>maven-dependency-tree</artifactId>
<version>3.0</version>
</dependency>
Release Notes - Apache Maven Dependency Tree - Version 3.0
Bug
* [MSHARED-422] Change DependencyGraphBuilder method signatures
Improvement
* [MSHARED-421] Change JDK + Maven requirements
* [MSHARED-371] Increase chance of java8 compliance by updating to
plexus-component-* 1.6
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
