[
http://jira.codehaus.org/browse/MVERSIONS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Connolly closed MVERSIONS-3.
------------------------------------
Resolution: Not A Bug
I'm unsure why I thought this was a bug.
The enforcer plugin is what you use to trap a plugin without a version
specified.
If we have a pom with a plugin referenced, and the version is not specified in
the pom we are running on, then the pom we are running on does not specify an
out of date version... the version is comming from a parent pom, and the parent
pom is the pom you should look at.
> display-plugin-updates does not identify the plugin version as not being
> provided when derived from the super-pom
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MVERSIONS-3
> URL: http://jira.codehaus.org/browse/MVERSIONS-3
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Affects Versions: 1.0-alpha-1, 1.0-alpha-2
> Reporter: Stephen Connolly
> Assignee: Stephen Connolly
> Priority: Minor
> Fix For: 1.0-alpha-3
>
>
> If the pom defines a plugin in the plugin management section, and that plugin
> definition does not include the plugin version, and the plugin definition is
> not repeated in the plugins section and no parent pom defines the plugin and
> the plugin version is being controled by the super-pom, the plugin should
> warn the user that the plugin version is unspecified.
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email