maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MNG-4100) Add maven-help-plugin to super pom
Date Sat, 21 Mar 2009 09:30:13 GMT


Benjamin Bentmann commented on MNG-4100:

Not sure that's a good idea. To get a newer version of a plugin being invoked ad-hoc from
the CLI, one can simply set the CLI flag "-U". These are just two chars that need to be typed
once. In contrast, if the Help Plugin was locked in the super POM, users who wanted to use
a later release would need to specify org.apache.maven.plugins:maven-help-plugin:version:help,
and that not just once but for each invocation. The qualified syntax is clumsy and seems counter-productive
for somebody seeking help.

The plugin management in the super POM was meant to bring a little stability to badly managed
builds. Considering the hassle required to override the super POM's plugin management for
a plugin that is primarily used from the CLI, the super POM is IMHO not the proper place for
such plugins.

> Add maven-help-plugin to super pom
> ----------------------------------
>                 Key: MNG-4100
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>    Affects Versions: 2.1.1
>            Reporter: Dan Fabulich
> A number of users where I work have recently upgraded to Maven 2.1, but when they try
to run the maven help plugin they're still on the old 2.0.2 version.  Some local repo weirdness,
clearing stuff out takes care of it, but it's not what you want when people are trying to
get help.
> We should add the maven-help-plugin to the super pom, and update it when new versions
of the help plugin are released.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message