Hi EJ, The fix for the bug mentioned was backported to the 1.1.x series and is available in 1.1.4 (http://archiva.apache.org/docs/1.1.4/release-notes.html). You would need to upgrade to this version to make it compatible with Maven 2.1.x. The release contains only this fix so there shouldn't be any problems with the upgrade.
Thanks, Deng On Sat, Oct 17, 2009 at 5:36 AM, EJ Ciramella <[email protected]>wrote: > Hi all - I just saw this article: > > > > http://www.sonatype.com/people/2009/07/from-apache-archiva-to-sonatype-n > exus/<http://www.sonatype.com/people/2009/07/from-apache-archiva-to-sonatype-n%0Aexus/> > > > > Where there's this: > > > > <snip> > > Apart from the incompatibility with Maven 2.1.0, nothing suggested that > the new version fixed any of our problems and there were few > improvements/new features at that time, due to lack of time by the > maintainers. > > </snip> > > > > Is this still the case? We're evaluating maven 2.2.1 right now. In > fact, I'm using it locally and have used it to deploy artifacts to our > archiva (1.1.3) server. > > > > I don't see any mention of this in release notes for archiva - where can > I get more detail? > >
