Return-Path: Delivered-To: apmail-maven-archiva-dev-archive@locus.apache.org Received: (qmail 50306 invoked from network); 4 Jun 2007 09:20:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Jun 2007 09:20:39 -0000 Received: (qmail 32670 invoked by uid 500); 4 Jun 2007 09:20:43 -0000 Delivered-To: apmail-maven-archiva-dev-archive@maven.apache.org Received: (qmail 32641 invoked by uid 500); 4 Jun 2007 09:20:43 -0000 Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: archiva-dev@maven.apache.org Delivered-To: mailing list archiva-dev@maven.apache.org Received: (qmail 32632 invoked by uid 99); 4 Jun 2007 09:20:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2007 02:20:43 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of nicolas.deloof@gmail.com designates 66.249.90.182 as permitted sender) Received: from [66.249.90.182] (HELO ik-out-1112.google.com) (66.249.90.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jun 2007 02:20:38 -0700 Received: by ik-out-1112.google.com with SMTP id c30so714097ika for ; Mon, 04 Jun 2007 02:20:17 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=A+eQfaMl5KAgINFPQvRg2vu1kHpw9qgBdDX4+EHfTpyztWPZjTEB4OKmzVJ1mjxhqfZs8dVglun66/ZBlds5xwlusA6VMn8RRVHOU81KuisakIxqf4ZMRc0mTkzOv7I7Hsrn7bFTlVSXOudCGBWurfbDxpsHttpWtFVWHsU3gyg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=o57TTGQqBkUenYU41hZONrQ1QOuWgD1ijXDHXLxIS6tXGhvdyhX5f19Uj6E6YmNMOKn4hRp3ZmabEGynR5S0GNvgmGr7yCzgYePiSduyc2PuuSSFENk51UqbGVEMAM3vlGac6W1OxMardnBO4uvYNAXCgaeCiLjgZOQBBGot2FA= Received: by 10.78.176.20 with SMTP id y20mr1902598hue.1180948810333; Mon, 04 Jun 2007 02:20:10 -0700 (PDT) Received: by 10.78.133.5 with HTTP; Mon, 4 Jun 2007 02:20:10 -0700 (PDT) Message-ID: <4c39e3030706040220s77fd0c2bnab179ee58451e8f5@mail.gmail.com> Date: Mon, 4 Jun 2007 11:20:10 +0200 From: "nicolas de loof" To: archiva-dev@maven.apache.org Subject: Re: [VOTE] Release Archiva 1.0-alpha-1 In-Reply-To: <760712e50706040141y6f197ba6j96afb6d0941a67d8@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_31798_11994472.1180948810302" References: <46607E27.5050301@apache.org> <466381B3.8090409@exist.com> <4c39e3030706040012m325f6524v2c736c5e37f3b773@mail.gmail.com> <760712e50706040141y6f197ba6j96afb6d0941a67d8@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_31798_11994472.1180948810302 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 : > > +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 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 : > > > > > > +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. > > > > > > > > > > > > > ------=_Part_31798_11994472.1180948810302--