Stephen,

on minotaur we have:

lrwxrwxr-x 1 jvanzyl apcvs 39 Jan 17 15:59 commons-collections-SNAPSHOT.jar -> commons-collections-20040102.233541.jar
lrwxrwxr-x 1 jvanzyl apcvs 43 Jan 17 15:59 commons-collections-SNAPSHOT.jar.md5 -> commons-collections-20040102.233541.jar.md5


and this is rsync'd to ibibilio under:

lrwxrwxrwx 1 dion maven 39 Mar 29 10:41 commons-collections-SNAPSHOT.jar -> commons-collections-20040102.233541.jar
lrwxrwxrwx 1 dion maven 43 Mar 29 10:41 commons-collections-SNAPSHOT.jar.md5 -> commons-collections-20040102.233541.jar.md5


I adjusted the symlink and version fil on minotaur to point to 3.0 and will verify that it updates properly onto ibibilio.

lrwxr-xr-x 1 mdiggory apcvs 27 May 7 20:04 commons-collections-SNAPSHOT.jar -> commons-collections-3.0.jar
lrwxr-xr-x 1 mdiggory apcvs 31 May 7 20:05 commons-collections-SNAPSHOT.jar.md5 -> commons-collections-3.0.jar.md5


-Mark

Stephen Colebourne wrote:
I've recently discovered that there is a bit of a rogue version of
commons-collections on ibiblio.

The jar named commons-collections-SNAPSHOT, is NOT the latest snapshot, and
in fact represents a time before the last release (3.0). This is causing
lots of misleading comments to float around the web.

Can all the *SNAPSHOT jars/md5s be removed from ibiblio commons-collections
please? And can the snapshot version be updated to point at the 3.0 release?
Or are there issues with doing this?

Thanks
Stephen



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to