Avoid releasing version 2.1 of commons-net. Use 2.1.1 or other instead
----------------------------------------------------------------------
Key: NET-336
URL: https://issues.apache.org/jira/browse/NET-336
Project: Commons Net
Issue Type: Task
Affects Versions: 2.1
Reporter: John Casey
Fix For: 2.1
I've been tracking some problems building jboss drools 5.1.0, specifically
where Maven can't locate commons-net 2.1.
http://anonsvn.jboss.org/repos/labs/labs/jbossrules/tags/5.1.0.34406.FINAL/pom.xml
(search for commons-net)
Looking in Maven central
(http://repo1.maven.org/maven2/commons-net/commons-net/) I cannot find
commons-net 2.1. Looking in the Maven-Central proxies from
repository.sonatype.org and repository.jboss.org, however, I *did* find it.
When I looked at the SVN tags for commons-net, I see that a 2.1 release was
rolled back in July 2010. It appears that this release, while rolled back in
SVN and on Maven central, has escaped into the wild before it could be
un-released. Maven and most Maven repository managers will NOT re-check a
non-snapshot version of an artifact once it's been downloaded. This is somewhat
like trying to un-send an email...
What this means is, if you release a "real" commons-net 2.1 sometime in the
future, you're going to have a ton of confusion over which version of that
artifact is in a user's Maven local repository and ultimately, his build
classpath. I strongly urge you to change the next release version to 2.1.1 or
something beyond 2.1, and simply write off that 2.1 version altogether.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
