Personally I think this should be done ASAP - at least its stops the problem from be being spread further.Could we come up with a decision on that one? I think it's important to fix this. Replace or delete the bogus 1.0 jar?
Same here ...what about a quick vote?
We need to copy the 1.0 tag and get it buildable again. The changes to the common maven config have meant that this tag is no longer buildable against the current setup and I haven't had much luck getting a working copy into the correct historical state to build using the old one.What's left to do for the 1.0.1 release?
Hm... that's unfortunate. So we would not provide any version 1.0 but only the 1.0.1 anymore? ...maybe we should then make an announcement, provide the jdiff and be sure 1.0.1 can replace 1.0 without any hurdles. WDYT? cheers -- Torsten
PGP.sig
Description: This is a digitally signed message part
