Ooh.  More on the original topic (big old trees and having to sort through
stuff)

mvn dependency:tree -Dverbose=true

That¹s a powerful tool in your pruning crusade.  Putting verbose on will
tell you about the decisions maven made in deciding which dependency
versions to keep and where they came from.  Using this, you could also
figure out what items you might like to put in <exclusions> block of
dependency declarations.  Most likely you aren't using everything in your
dependencies and you can figure out what fat you want to trimŠ

Of course, this is the most intrusive and time consuming optionŠ  but I
suspect that it will yield the greatest results.




Thanks,

Roy Lyons
Senior Configuration Engineer
(312) 648-3659 [w] 
(773) 551-8335 [c] 
roy.ly...@cmegroup.com
<mailto:roy.ly...@cmegroup.com?subject=Contact%20from%20email%20signature>
CME Group 
20 S. Wacker Drive
Chicago, Illinois 60606
Self Help 
https://wiki.chicago.cme.com/confluence/display/CM/Home






On 10/11/12 9:02 AM, "Barrie Treloar" <baerr...@gmail.com> wrote:

>On Thu, Oct 11, 2012 at 6:57 PM, Wang, Simon <yunfeng.w...@ebay.com>
>wrote:
>> Hi, Barrie,
>>    Ask a stupid question about enforcer plugin.
>> I added enforcer plugin into project pom like this:
>>                         <plugin>
>>                 
>><groupId>org.apache.maven.plugins</groupId>
>>                 
>><artifactId>maven-enforcer-plugin</artifactId>
>>                                         <version>1.1.1</version>
>>                                         <executions>
>>                                           <execution>
>>                                                 <id>enforce</id>
>>                                                 <configuration>
>>                                                         <rules>
>>                 
>><DependencyConvergence/>
>>                                                         </rules>
>>                                                 </configuration>
>>                                                 <goals>
>>                                                   <goal>enforce</goal>
>>                                                 </goals>
>>                                           </execution>
>>                                         </executions>
>>                         </plugin>
>
>I'm not sure, your example is a copy-and-paste of
>http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html
>
>However I would normally expect things to be case sensitive and the
>rule index (http://maven.apache.org/enforcer/enforcer-rules/index.html)
>uses "dependencyConvergence"
>
>You could try that instead.
>If it does work, I'd file a bug against the enforcer documentation.
>
>Also, I dont expect dependencyConvergence to actually help you with
>performance.
>Try running maven with -X and then scouring the copious amount of
>output to see what it is doing and where it is spending its time.
>Always measure before you optimize.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>For additional commands, e-mail: users-h...@maven.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to