[
https://jira.codehaus.org/browse/MVERSIONS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287539#comment-287539
]
Bob Fields commented on MVERSIONS-144:
--------------------------------------
A more complete solution would use pattern matching instead of .equals
(ignoreVersions.contains(version) in the code patch). The pattern should be
able to be applied globally as well as at the group/artifact level. For
example, I want to exclude release updates that include 'alpha', 'beta', or
'RC', or versions that don't follow the three or four part numbering scheme. Or
I want to restrict the update checks to a version range when I can't update to
the next major version but I still want to know when there are minor release
updates within the version I am using. Here are examples from andromda:
[INFO] --- versions-maven-plugin:1.2:display-dependency-updates (default-cli) @
andromda-samples ---
[INFO] The following dependencies in Dependency Management have newer versions:
[INFO] antlr:antlr ........................................ 2.7.7 -> 20030911
[INFO] commons-cli:commons-cli ....................... 1.2 -> 20040117.000000
[INFO] dom4j:dom4j ................................. 1.6.1 -> 20040902.021138
[INFO] javax.servlet:servlet-api ......................... 2.5 -> 3.0-alpha-1
[INFO] javax.servlet.jsp:jsp-api ......................... 2.2.1-b03 -> 2.2.1
[INFO] org.apache.maven:maven-core ........................... 2.2.1 -> 3.0.3
[INFO] org.apache.maven:maven-plugin-api ..................... 2.2.1 -> 3.0.3
[INFO] org.apache.velocity:velocity ...................... 1.6.4 -> 1.7-beta1
[INFO] org.codehaus.groovy:groovy-all ................. 1.8.0 -> 2.0.0-beta-2
[INFO] commons-logging:commons-logging ......... 1.1.1 -> 99.0-does-not-exist
[INFO] org.jboss.spec:jboss-javaee-web-6.0 ....... 2.0.0.Final -> 3.0.0.Beta1
[INFO] org.mortbay.jetty:jetty-maven-plugin ... 8.0.3.v20111011 -> 8.1.0.RC1
> Allow excluding certain versions of artifacts
> ---------------------------------------------
>
> Key: MVERSIONS-144
> URL: https://jira.codehaus.org/browse/MVERSIONS-144
> Project: Maven 2.x Versions Plugin
> Issue Type: New Feature
> Reporter: Will May
> Priority: Minor
> Attachments:
> Allow_certain_artifact_versions_to_be_excluded_from_consideration.patch,
> Allow_certain_artifact_versions_to_be_excluded_from_consideration_with_test.patch
>
>
> As some popular projects have released versions with invalid version numbers
> such as asm (version number 20041228.180559), it would be useful to be able
> to ignore certain versions when checking for updates. This functionality
> could also be used to exclude a version which has a known vulnerability.
> This patch doesn't include any unit tests for the new functionality as it's
> only a quick go. I've tested it locally and it correctly ignored the various
> commons-configuration and asm invalid versions. To add a unit test, it would
> be easier to use something such as Mockito but that is Java 5+ only. Are
> there any plans to upgrade to Java 5? Or are there any Java 1.4 mocking
> frameworks?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
