I tried to build maven 1.0 clean today and found out that on Sep 2,
commons-jelly and a few of its tag libs had changed on ibiblio. These
were already released jars that changed size. I checked around and
discovered the source of the change seems to be java-repository at
Apache.

Any ideas how this happened?

One particular offending file:
> ls -l /www/www.apache.org/dist/java-repository/commons-jelly/jars/ | grep 
> 20030902
-rw-r--r--  1 mdiggory  jakarta  161479 Sep  2 00:08
commons-jelly-20030902.160215.jar
> md5 
> </www/www.apache.org/dist/java-repository/commons-jelly/jars/commons-jelly-20030902.160215.jar
d1e3117b90f697e6503e4ddf76bc0402

The original:
[EMAIL PROTECTED] repaired]$ md5sum
commons-jelly/jars/commons-jelly-20030902.160215.jar
b171e535366191e437cff6d64df33561 
commons-jelly/jars/commons-jelly-20030902.160215.jar
[EMAIL PROTECTED] repaired]$ ls -l
commons-jelly/jars/commons-jelly-20030902.160215.jar
-rwxr-xr-x    1 maven    users      154418 Sep 28 09:00
commons-jelly/jars/commons-jelly-20030902.160215.jar
(this is identical to the version distributed with Maven 1.0 back in July)

The full list from the Maven 1.0 build that differ:
commons-jelly/jars/commons-jelly-20030902.160215.jar
commons-jelly/jars/commons-jelly-tags-antlr-20030211.143720.jar
commons-jelly/jars/commons-jelly-tags-define-20030211.142932.jar
commons-jelly/jars/commons-jelly-tags-html-20030317.100924.jar
commons-jelly/jars/commons-jelly-tags-interaction-20030211.143817.jar
commons-jelly/jars/commons-jelly-tags-jsl-20030211.143151.jar
commons-jelly/jars/commons-jelly-tags-log-20030211.142821.jar
commons-jelly/jars/commons-jelly-tags-swing-20030211.143925.jar
commons-jelly/jars/commons-jelly-tags-util-20030211.141939.jar
commons-jelly/jars/commons-jelly-tags-velocity-20030303.205659.jar
commons-jelly/jars/commons-jelly-tags-xml-20030211.142705.jar

I have corrected the versions on ibiblio (being newer, they should
stay that way), but left Apache alone to find out what happened. I'd
really like to know if we can resolve this to avoid it in the future,
and to see if anything else was possibly affected.

Thanks,
Brett

Reply via email to