Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (athena.apache.org: domain of bmathus@gmail.com designates
 74.125.83.46 as permitted sender)
MIME-Version: 1.0
Sender: bmathus@gmail.com
In-Reply-To: 
 <CAKDUN1uQ+xAq5Pk0b706JhpWESDn4dQ2KHUQuzWXss4Fmj8uvQ@mail.gmail.com>
References: 
 <CAKDUN1tmwTDLY6m=+j8pMHfhnsrOiZ3RAeZwNNFRPCNkXGcx4A@mail.gmail.com>
 <83b053da2b8147291bf8b6f369a4758a.squirrel@www.mosabuam.com>
 <CAKDUN1uQ+xAq5Pk0b706JhpWESDn4dQ2KHUQuzWXss4Fmj8uvQ@mail.gmail.com>
From: Baptiste MATHUS <bmathus@batmat.net>
Date: Thu, 18 Apr 2013 21:24:02 +0200
Message-ID: 
 <CANWgJS6ggZmG3ZwEA+v4BzAeKZ5c2er=xoOiN88BDyPewcNwYg@mail.gmail.com>
Subject: Re: The archetype/archetype-catalog mess
To: Maven Developers List <dev@maven.apache.org>
Content-Type: multipart/alternative; boundary=089e01681310c3555404daa78c84

--089e01681310c3555404daa78c84
Content-Type: text/plain; charset=UTF-8

+1.

Though I'd personally be inclined to just go m3+ directly, I suppose this
would be a bit more progressive for users to release a last m2 compatible
version before going m3+.
That'd be the occasion to state clearly this is the last m2-compatible in
the release notes.

Sure, this strategy is only valid if ARCHETYPE-427 and ARCHETYPE-358 are
fixable without too much hassle.

Cheers


2013/4/18 Anders Hammar <anders@hammar.net>

> Heck, we might even go v3.0 with this change and remove a lot of garbage
> that I've found in the code. And delete the create goal. :-)
> Maybe even require Maven 3.0+ to simplify the code. Or maybe that's taking
> this a little bit to far?
>
> /Anders
>
>
> On Thu, Apr 18, 2013 at 6:41 PM, Manfred Moser <manfred@simpligility.com
> >wrote:
>
> > You would be earning a lot of brownie points I am sure! There are a bunch
> > of open questions around this and the perception that the archetype
> system
> > is pretty much dead on stackoverflow and other places. This could fix a
> > lot of those concerns..
> >
> > manfred
> >
> > > Currently, maven-archetype-plugin ignores the configured Maven
> > > infrastructure when fetching the archetype-catalog. That is, it is
> > > hard-coded to get the catalog from central. This causes problems in
> > > environments where Internet access is restricted and a MRM is used.
> Also,
> > > in cases where Internet is accessible I think the current behavior
> where
> > > configured repositories/mirrors are ignored is strange. I would expect
> my
> > > Maven configuration to be honored and the catalog to downloaded from my
> > > configured remote repos (incl. mirrors).
> > >
> > > Do anyone object if I do some drastic changes to this logic in the
> > plugin?
> > > I'm thinking that the plugin should follow the Maven configuration and
> > not
> > > have anything hard-coded in itself wrt where to get the archetype
> > > catalog(s) from.
> > > Related tickets are ARCHETYPE-427 and ARCHETYPE-358 primarily, but it
> > > touches on other ones as well.
> > >
> > > /Anders
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>


-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

--089e01681310c3555404daa78c84--