archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas de loof" <>
Subject Re: Let's release Archiva
Date Tue, 10 Apr 2007 05:18:08 GMT
I'm also using archiva for both my maven1 and maven2 projects.

I'll just warn that there is a thread-safety issue with wagon (WAGON-79)
that introduces ConcurrentModificationException.

I applied MRM-153 + 211 + 212 patches to my snapshot build. This allow me to
have only one repository for both maven versions. MRM-212 is a requirement
to make archiva usable as a proxy on repo1.

For those reason, I'd vote -1 (as a user) for a release based on current


2007/4/10, Brett Porter <>:
> I'm also in favour of this. I've been using it myself, and it's
> stable enough for my purposes.
> I've been holding back on asking the same thing as I know Joakim has
> been doing significant work on the branch and I've been expecting
> some details here any day now. Joakim - can you update us on what
> you've been doing and how it will impact trunk?
> Based on that, I think we need to make a decision about whether to
> cut a release from the current trunk for all those that have ended up
> using it, or push forward with the new code. But either way, we need
> a release now.
> - Brett
> On 10/04/2007, at 1:48 PM, Wendy Smoak wrote:
> > I took a look at archiva/trunk, and the only remaining snapshot
> > dependencies I see are from maven-app-configuration.  That vote has
> > passed and is just waiting for the staged binaries to be copied over
> > to the synced repo.
> >
> > Once that's done, I'd like to tag and release archiva/trunk.  It
> > works, it already has users, and we should have an official release.
> >
> > Thoughts?
> >
> > --
> > Wendy

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message