[ http://jira.codehaus.org/browse/MOJO-182?page=comments#action_54596 ]
Brian Fox commented on MOJO-182: -------------------------------- is this the same as the recently added pom tools? > maven-model-plugin > ------------------ > > Key: MOJO-182 > URL: http://jira.codehaus.org/browse/MOJO-182 > Project: Mojo > Type: New Feature > Reporter: David Hawkins > Priority: Minor > > > I created a plugin for dependency management and pom editing via the command > line. My initial goal was to create a plugin which would show me a list of > my dependencies and determine if any of them needed to be updated to a later > version. I really couldn't find an easy way to do this for a project with > a large number of dependencies. As soon as I started working with dependency > resolution, the plugin quickly diverged into including transitive dependency > conflict resolution and pom editing. > See this page for more information, screen shots, and the src download: > http://www.famhq.com/maven/maven-model-plugin/announcement.html > My goal is to add it to the Mojo project if people find it as useful as I do. > Highlights: > * Displays project dependencies and the latest version of each. (You can > enable/disable the use of snapshots when determining the latest version) > You have the option of setting all to the latest version or manually > editing each. > * Transitive dependencies > * Starting Points - display a tree of the transitive dependencies that > are included by a dependency. (see example below) > * End Points - displays a list of all transitive dependencies that are > included in the compilation classpath. Each dependency will show if > there are any conflicting versions of the groupId:artifactId that were > evaluated when resolving the artifacts. You can also dive into any > transitive dependency and view a tree of all the possible paths that > can include that dependency. > * Edit nearly any element of the pom via a console UI. Includes list of > values for fields with constrained values. > * All model fields are discovered via reflection and editors are dynamic so > that future changes to the model should work without modification of this > plugin. > * When adding/editing dependencies and plugins you are shown a list of > available versions to select from. > * Dependency versions can be ranges and the versions selected by the range > are displayed in the list of versions. > * Performs validation on the model via the DefaultModelValidator. Will not > save a pom that will not validate. > * You can make changes to the model and view how they affect transitive > dependencies without actually saving the model. This allows you to tweak > the settings or even revert all of your changes. > --David -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
