patch is up to date and issue has been reopened (as previous patch was applied but didn't work using the DAV "/repository" URI.
2007/4/11, Arnaud HERITIER <[EMAIL PROTECTED]>:
On 11/04/07, nicolas de loof <[EMAIL PROTECTED]> wrote: > > I have my archiva deployed and running, so I can wait for a merge for any > further enhancements. I allready had to adapt MRM153 patch for the > "/proxy" > to "/repository" URI changes. I'll follow changes made on trunk to update > my > snapshot, and propose patches when required. Did you attached the updated patches to the issues ? Just for my info, as I missed original discution about branching, what does > this parallel work target as enhancement for archiva ? > > Nico. > > 2007/4/10, Wendy Smoak <[EMAIL PROTECTED]>: > > > > On 4/10/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote: > > > > > Also, the work that is identified by MRM-153 + 211 + 212 are moot in > the > > > branch, as other, more fundamental solutions has been worked out for > > > dealing with remote repositories, checksum policy, and maven 1 > clients. > > ... > > > Any release of trunk should be considered pre-1.0 (not even alpha-1) > as > > > it is so broken. > > > > Thanks for the detailed list of issues. And I edited out a suggestion > > to release it as 0.9 and leave the 1.0 version for the work on the > > branch, so let's go with that, assuming... > > > > Arnaud, Nicolas, are you planning to work on trunk and get the fixes > > in there, or are you content to wait on the branch? > > > > -- > > Wendy > > >
