java - "Using Maven 2 dependency tree to get verbose output, which may be inconsistent with actual Maven 3 resolution" -


i have changed used version of maven-dependency-plugin 2.8 2.10. now, when run mvn dependency:tree -dverbose see following warning:

[warning] using maven 2 dependency tree verbose output, may inconsistent actual maven 3 resolution 

the version of maven using is

apache maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14t18:37:52+01:00) 
  • can fix or avoid anyhow?
  • was case maven 2 used -dverbose output have added warning?

the explanation problem can found @ official documentation:

verbose whether include omitted nodes in serialized dependency tree. notice feature uses maven 2 algorithm , may give wrong results when used maven 3.

have @ line 245 of treemojo.java version 2.10:

if ( verbose ) {     // verbose mode force maven 2 dependency tree component use     if ( ! ismaven2x() )     {         getlog().warn( "using maven 2 dependency tree verbose output, "                            + "which may inconsistent actual maven 3 resolution" );     }     dependencytreestring =         serializeverbosedependencytree( dependencytreebuilder.builddependencytree( project,                                                                                    localrepository,                                                                                    artifactfilter ) ); } 

it prints warning if maven 2 not used.

now @ line 243 of treemojo.java version 2.8:

if ( verbose ) {     // verbose mode force maven 2 dependency tree component use     dependencytreestring =         serializeverbosedependencytree( dependencytreebuilder.builddependencytree( project,                                                                                    localrepository,                                                                                    artifactfilter ) ); } 

the warning logging not exist there, so:

was case maven 2 used -dverbose output have added warning?

yes, warning has been added since version 2.8.

can fix or avoid anyhow?

i guess not, without ignoring warning log messages, or editing source code.

however, can see, maven 2 functionality used in 2.8. rid of in later versions when migrate dependency:tree -dverbose use maven 3 functionality.


Comments

Popular posts from this blog

How to run C# code using mono without Xamarin in Android? -

html - grunt SVG to webfont -

c# - SharpSsh Command Execution -