archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas de loof" <nicolas.del...@gmail.com>
Subject Re: [VOTE] Release Archiva 1.0-alpha-1
Date Mon, 04 Jun 2007 09:20:10 GMT
You're right, I missunderstood the default configuration of network proxies.
I just had to reconfigure the network proxies to point to my managed repo.

What is the default "internal" managed repo ?


2007/6/4, Fabrice Bellingard <bellingard@gmail.com>:
>
> +1, I'm happy with it already. :-)
>
> Nicolas, getting artifacts from proxied remote repositories works fine for
> me (at least it used to 3 days ago...). If I can help...
>
> Fabrice.
>
> On 6/4/07, nicolas de loof <nicolas.deloof@gmail.com> wrote:
> >
> > +1 as a new clean codebase for enhancements, based on 0.9 features set.
> >
> > My personnal feedback on current features :
> >
> > + Verry clean configuration UI
> > - Getting artifacts from a proxied repository doesn't work
> > - Lack of support for Maven 1 (requests are not converted to get
> artifacts
> > from a maven2 managed repo)
> > - wagon-provider-api 1.0 has a ConcurrentModificationException issue
> > (WAGON-79)
> >
> >
> > 2007/6/4, Maria Odea Ching <oching@exist.com>:
> > >
> > > +1
> > >
> > > Everything on the release notes seems to be in place.
> > > Thanks Joakim :-)
> > >
> > > -Deng
> > >
> > > Joakim Erdfelt wrote:
> > > > Archiva 1.0-alpha-1 was tagged and built this afternoon.
> > > >
> > > > The proposed distribution, including binary distributions, and
> > > > signatures can be found here:
> > > >
> > > >  http://people.apache.org/builds/maven/archiva/1.0-alpha-1/
> > > >
> > > > To keep up with the trend started by Wendy Smoak (sorta):
> > > > The 1.0-alpha-1 staged copy was setup and configured to point to
> > > > a pre-built repository, and then used to build the next archiva
> > > > snapshot (1.0-alpha-2-SNAPSHOT) in archiva/trunk.
> > > >
> > > > This will be Archiva's first release with a proper database, and
> > > > is intended to get a testable baseline of the archiva feature set
> > > > into the hands of all interested individuals.
> > > >
> > > > The list of issues identified and closed with this release can
> > > > be found below:
> > > >
> > > >  Archiva 1.0-alpha-1 Release Notes:
> > > >
> > > >
> > >
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10980&styleName=Html&version=13443
> > > >
> > > >
> > > > This is an alpha release, and as such, has bugs.
> > > >
> > > > Once people have a chance to kick the prototype tires, and look
> > around,
> > > > the most urgent jira tickets will be addressed quickly for a
> > 1.0-alpha-2
> > > > release, with an expected release 1 to 2 weeks after this one.
> > > >
> > > > Known issues include documentation, problems with proxying, problems
> > > > running the webapp on Tomcat, missing reporting, empty or inaccurate
> > > > dependency tree information, and poor grammar.
> > > > These and other issues can be tracked at the URL below:
> > > >
> > > >  Archiva 1.0-alpha-2 Open Issues:
> > > >
> > >
> >
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10980&fixfor=13518
> > > >
> > > >
> > > > Once you have had a chance to examine the distribution, please cast
> > > > your vote.  We welcome votes and feedback from all community
> members.
> > > >
> > > > [ ]  +1  Release it!
> > > > [ ]   0
> > > > [ ]  -1  Don't release it, because...
> > > >
> > > > 72 hours ends Monday afternoon (GMT -5)
> > > > If you need more time, just ask.
> > > >
> > >
> > >
> >
>

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