Mailing-List: contact archiva-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: archiva-dev@maven.apache.org
Received-SPF: pass (athena.apache.org: domain of nicolas.deloof@gmail.com
 designates 64.233.182.188 as permitted sender)
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:content-transfer-encoding:content-disposition:references;
        b=rDBohp2nUZSPkiPaBVLXngBCmS9lqSk9gbgR5MpY6zT4Ojhk93w4blOEEueeMfRcFCz2J++9qxv5hU6EXvT7wc1h5cLKifwh9gdOdKPeqEqQUu9UlOAcp7eshouzRwJQA9ZLSH67MfeMDkCUyeIdhfooxdN+HxGZWsk86ZbZcKo=
Message-ID: <4c39e3030709140915x350446c4lcc6dcae19e9570db@mail.gmail.com>
Date: Fri, 14 Sep 2007 18:15:09 +0200
From: "nicolas de loof" <nicolas.deloof@gmail.com>
To: archiva-dev@maven.apache.org
Subject: Re: Archiva 1.0-beta-2 Release Schedule
In-Reply-To: <4c39e3030709140904x4c47e140ia9b3ba35caf1dfd7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46E9080E.8040002@exist.com>
	 <262c6c680709130310t437b3d52wbe20a9d89f3ed29@mail.gmail.com>
	 <B224DD3D-796F-46C4-B847-6F91583CFEA0@apache.org>
	 <262c6c680709130454r3cf9d489l5177f072b9d6dff2@mail.gmail.com>
	 <4c39e3030709130734o7f1f5c15pf69c1fbe2cbdc540@mail.gmail.com>
	 <1E9FD682-6C19-4223-A0AC-E2EAB46AA9AC@apache.org>
	 <4c39e3030709140904x4c47e140ia9b3ba35caf1dfd7@mail.gmail.com>

Not sure about this, but MRM-308 seems to be resolved in SVN :

my managed repo uses default layout and I can get both :
   http://localhost:8080/archiva/repository/internal/ant/jars/ant-1.6.5.jar
and
   http://localhost:8080/archiva/repository/internal//ant/ant/1.6.5/ant-1.6.5.jar

MRM-211 is still blocking to use archiva with maven1. It only requires
an entry in components.xml to be solved !

Nico.

2007/9/14, nicolas de loof <nicolas.deloof@gmail.com>:
> I just attached my patch (MRM153-1.0-beta-2.patch).
> -> http://jira.codehaus.org/browse/MRM-153
>
> I tested it on my corporate archiva instance to get servlet-api-2.3
> using various paths :
>
> maven2 (javax/servlet/servlet-api/2.3/servlet-api-2.3.jar)
> maven2 with "client-side" relocation (servletapi/2.3/servletapi-2.3.pom)
>
> maven1 (javax.servlet/jars/servlet-api-2.3.jar)
> maven1 with "server-side" relocation (servletapi/2.3/servletapi-2.3.jar)
>
> I need help to write some integration test to document/instrument this
> feature, as I'm not familiar with both plexus and servlets automated
> testing.
>
> Nico
>
>
> 2007/9/13, Brett Porter <brett@apache.org>:
> > Thanks!
> >
> > On 14/09/2007, at 12:34 AM, nicolas de loof wrote:
> >
> > > I have lot's of maven1 project on my side.
> > > I'll attach an updated patch as soon as possible for MRM-153.
> > >
> > > Nico.
> > >
> > > 2007/9/13, Arnaud HERITIER <aheritier@gmail.com>:
> > >> I have less and less m1 projects around me ;-)
> > >> When I find one, I move it to m2 ;-)
> > >>
> > >> Arnaud
> > >>
> > >> On 13/09/2007, Brett Porter <brett@apache.org> wrote:
> > >>>
> > >>> I agree. Actually, a couple of these already have patches. I was
> > >>> going to run through and apply them but if you're actively using the
> > >>> maven1 stuff and can test it better then by all means assign them to
> > >>> yourself and put them in if they work :)
> > >>>
> > >>> Cheers,
> > >>> Brett
> > >>>
> > >>> On 13/09/2007, at 8:10 PM, Arnaud HERITIER wrote:
> > >>>
> > >>>> I hope that maven 1 issues [MRM-153, MRM-211, MRM-308] will be
> > >>>> fixed in the
> > >>>> next beta. when it worked it was very useful to help companies to
> > >>>> migrate
> > >>>> maven 1 projects to maven 2.
> > >>>>
> > >>>> The problem in MRM-243 isn't in archiva itself but it prevents to
> > >>>> deploy
> > >>>> artifact from a CI server if archiva is on windows (it creates too
> > >>>> many
> > >>>> build failures).
> > >>>>
> > >>>> MRM-385 has to be fixed before the release !
> > >>>>
> > >>>> Arnaud
> > >>>>
> > >>>> On 13/09/2007, Maria Odea Ching <oching@exist.com> wrote:
> > >>>>>
> > >>>>> Hi Everyone,
> > >>>>>
> > >>>>> I will prepare the release of Archiva 1.0-beta-2 on Sept. 15
> > >>>>> (Saturday,
> > >>>>> my time). :-)
> > >>>>>
> > >>>>> Below are the jira issues scheduled for this release, some of
> > >>>>> which will
> > >>>>> probably be moved to
> > >>>>> the next beta release if it won't make it on Saturday.
> > >>>>>
> > >>>>>
> > >>>>> 1. Closed/Resolved:
> > >>>>>
> > >>>>> * [MRM-144] - fix miscellaneous tasks listed in important TODO
> > >>>>> items
> > >>>>> * [MRM-374] - Changes aren't saved when updating Archiva Managed
> > >>>>> Snapshot Repository
> > >>>>> * [MRM-383] - Unable to add new file types for Repository Scanning
> > >>>>> * [MRM-392] - pressing 'return' in the blacklist/whitelist form
> > >>>>> field
> > >>>>> submits whole form and validates, not pressing associated button
> > >>>>> * [MRM-393] - Can't delete blacklist/whitelist pattern
> > >>>>> * [MRM-407] - "Scanned" is always set to true even if unchecked in
> > >>>>> the
> > >>>>> Edit Repository page
> > >>>>> * [MRM-408] - The mvn deploy:deploy-file command gives "Parent
> > >>>>> doesn't
> > >>>>> exist" in a fresh install
> > >>>>> * [MRM-409] - No checking of invalid poms or artifacts during
> > >>>>> repository
> > >>>>> scanning resulting to some objects not being found on the database
> > >>>>> * [MRM-436] - incorrect default cron expression for snapshots
> > >>>>> repository
> > >>>>> * [MRM-438] - broken images in the download box on the artifact
> > >>>>> page
> > >>>>> * [MRM-441] - removing a "remote repository" should not present
> > >>>>> the page
> > >>>>> about handling content
> > >>>>> * [MRM-449] - improvement to the reports form group search
> > >>>>> * [MRM-450] - change default label for repository ID report
> > >>>>> search to
> > >>>>> "All repositories" instead of ""
> > >>>>> * [MRM-453] - Create missing tests for repository purge
> > >>>>> * [MRM-456] - current configuration code is too likely to complain
> > >>>>> about
> > >>>>> multiple sources
> > >>>>> * [MRM-457] - don't display the snapshot removal options in the
> > >>>>> repository list page if snapshots are not included
> > >>>>> * [MRM-462] - separate configuration of managed repositories from
> > >>>>> remote
> > >>>>> repositories
> > >>>>> * [MRM-463] - Metadata merging doesn't work.
> > >>>>> * [MRM-465] - [Load Testing] When asking for pages that require
> > >>>>> the
> > >>>>> effective-pom in high load, app becomes unresponsive.
> > >>>>> * [MRM-467] - 500 error when user requested the dependency tree
> > >>>>> for
> > >>>>> artifact
> > >>>>> * [MRM-471] - Create a sample project that demonstrates how a
> > >>>>> component
> > >>>>> can be plugged into Archiva.
> > >>>>> * [MRM-472] - Re-enabled metadata tests in archiva-proxy
> > >>>>> * [MRM-473] - Fix the proxy code (and possibly the tests) to
> > >>>>> ensure
> > >>>>> proper merging of metadata.xml files.
> > >>>>> * [MRM-474] - Create tests for non-snapshot metadata merging
> > >>>>> * [MRM-475] - Create tests for snapshot metadata merging
> > >>>>> * [MRM-496] - adding a proxy connector action is not working after
> > >>>>> repository changes
> > >>>>>
> > >>>>>
> > >>>>> 2. Open/In-Progress:
> > >>>>>
> > >>>>> * [MRM-128] - better handling of jar artifacts without a pom
> > >>>>> * [MRM-130] - improve search results page
> > >>>>> * [MRM-153] - when used as a maven1 proxy, Archiva should handle
> > >>>>> relocation from maven2 poms
> > >>>>> * [MRM-196] - paginate results
> > >>>>> * [MRM-203] - Reports should be public, not an administration
> > >>>>> feature
> > >>>>> * [MRM-211] - Cannot use Archiva to get Maven1 Plugins
> > >>>>> * [MRM-243] - 507 Insufficient Storage when deploying artifact
> > >>>>> with webdav
> > >>>>> * [MRM-308] - Maven1 requests are not served
> > >>>>> * [MRM-309] - relocated artifacts are not delivered
> > >>>>> * [MRM-320] - ProxiedDavServer breaks update policy
> > >>>>> * [MRM-385] - Maven config docs refer to /proxy urls
> > >>>>> * [MRM-398] - configure guest access by default for pre-configured
> > >>>>> repositories
> > >>>>> * [MRM-428] - managed and remote repositories with same name
> > >>>>> causes
> > >>>>> problems
> > >>>>> * [MRM-432] - Proxy Connectors are unable to download artifacts
> > >>>>> with
> > >>>>> alpha numerical version numbers
> > >>>>> * [MRM-433] - Artifacts file types aren't take in account
> > >>>>> * [MRM-435] - need to review repository defaults
> > >>>>> * [MRM-437] - admin editing of proxy connectors fails in multiple
> > >>>>> instances
> > >>>>> * [MRM-444] - intermittent test failures on proxy
> > >>>>> * [MRM-458] - the NOTICE file is overzealous in declaring
> > >>>>> dependencies
> > >>>>> * [MRM-459] - prune the distributed dependencies
> > >>>>> * [MRM-460] - invalid cache policy
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> Thanks,
> > >>>>> Deng
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>> --
> > >>>> ..........................................................
> > >>>> Arnaud HERITIER
> > >>>> ..........................................................
> > >>>> OCTO Technology - aheritier AT octo DOT com
> > >>>> www.octo.com | blog.octo.com
> > >>>> ..........................................................
> > >>>> ASF - aheritier AT apache DOT org
> > >>>> www.apache.org | maven.apache.org
> > >>>> ...........................................................
> > >>>
> > >>> --
> > >>> Brett Porter - brett@apache.org
> > >>> Blog: http://www.devzuz.org/blogs/bporter/
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> ..........................................................
> > >> Arnaud HERITIER
> > >> ..........................................................
> > >> OCTO Technology - aheritier AT octo DOT com
> > >> www.octo.com | blog.octo.com
> > >> ..........................................................
> > >> ASF - aheritier AT apache DOT org
> > >> www.apache.org | maven.apache.org
> > >> ...........................................................
> > >>
> >
> > --
> > Brett Porter - brett@apache.org
> > Blog: http://www.devzuz.org/blogs/bporter/
> >
>