Fair enough, we can move that forward if we think it's an issue.
If the results are back to normal, which they seem to do, I'm already
quite happy.
-Robert
Op Fri, 15 Jun 2012 22:25:27 +0200 schreef Hervé BOUTEMY
:
I don't know what happens: I checked, the result with mvn2 and mvn3 is
t
I don't know what happens: I checked, the result with mvn2 and mvn3 is the
same. I don't explain downloaded info
Regards,
Hervé
Le jeudi 14 juin 2012 22:38:04 Robert Scholte a écrit :
> Hi Hervé,
>
> this already looks better, but I'm still a bit surprised be the result.
> After removing all m
Hi Hervé,
this already looks better, but I'm still a bit surprised be the result.
After removing all maven-plugin-api's I got this result:
E:\java-workspace\codehaus-mojo\idlj-maven-plugin>mvn
org.apache.maven.plugins:maven-project-info-reports-plugin:2.5-SNAPSHOT:dependencies
[INFO] Scanning
Sounds good idea !
I'm a bit out of time this week.
I will have a look early next week.
2012/6/11 Hervé BOUTEMY :
> thank you
>
> BTW, that's the moment to ask for review
>
> To sum up, I created a layer on top of maven-dependency-tree for Maven 2 and
> Maven3+Aether and tested it on MPIR
> AFAIK
thank you
BTW, that's the moment to ask for review
To sum up, I created a layer on top of maven-dependency-tree for Maven 2 and
Maven3+Aether and tested it on MPIR
AFAIK, the result is a MPIR dependencies report that works finally as well with
Maven 2 and Maven 3 (tested with 2.2.1 and 3.0.4).
