[X] +0 "Let's release it, even if I'd expect some more fixes !" Not voting 0 or -1 as some stable archiva release is expected for too long, but archiva CANNOT be used with legacy maven1 projects as it cannot serve jaxen-1.0-FCS-full, that is used by some maven1 core plugins
Applying my MRM-594 first patch would fix this until a consensus is found on how to support legacy requests. I myself try to promote the use of maven2, but many project still use maven1 (don't have time / money / knoledge to migrate), and maintenance requires old m1 builds to work. Nico. 2007/11/23, Maria Odea Ching <[EMAIL PROTECTED]>: > > Hi Everyone, > > The Archiva 1.0 release candidate has been prepared. Regressions for m1 > proxy requests found in 1.0-beta-4 have been fixed and the important > documents for the site have been completed. > > You can take a look at the release notes for Archiva 1.0 here: > > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12113&styleName=Text&projectId=10980&Create=Create > > > While the binaries, including the sources, signatures and checksums, can > be > downloaded here: > > http://people.apache.org/builds/maven/archiva/1.0/ > > > Everyone is encouraged to vote and give their feedback. Please make sure > to > test it before voting ;-) > > [ ] +1 Release it! > [ ] 0 > [ ] -1 Don't release it, because... > > The vote will be open for 72 hours. So, cast your votes now.. > > > Thanks, > Deng >
