[
http://jira.codehaus.org/browse/MVERSIONS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=255668#action_255668
]
Stephen Connolly commented on MVERSIONS-143:
--------------------------------------------
If people mess up the repository there is nothing that we can do.
if they were changing version numbering scheme they should have changed groupId
or artifactId as well at the same time.
If you want to ignore those later versions for your projects, then add a range
restriction to the dependency (might require using a property to specify the
version)
> Wrong deployed plugins
> ----------------------
>
> Key: MVERSIONS-143
> URL: http://jira.codehaus.org/browse/MVERSIONS-143
> Project: Maven 2.x Versions Plugin
> Issue Type: Bug
> Reporter: Andres Gomez Casanova
>
> Hi,
> I'm using commons configuration in my project, and when I execute versions
> plugin it say that the newest version is 20040121, but in fact, this is an
> old bad deployed where the timestamp was inserted in the version.
> I would like the plugin to detect this kind of problems and correct them.
> http://mvnrepository.com/artifact/commons-configuration/commons-configuration
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] commons-configuration:commons-configuration ... 1.6 ->
> 20040121.140929
--
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
