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 (nike.apache.org: domain of manfred@simpligility.com
 designates 69.89.13.14 as permitted sender)
Received-SPF: pass (vancouverislandjavausergroup.virtual.vps-host.net: domain
 of manfred@simpligility.com designates 127.0.0.1 as permitted sender)
 receiver=vancouverislandjavausergroup.virtual.vps-host.net;
 client-ip=127.0.0.1; helo=vancouverislandjavausergroup.virtual.vps-host.net;
 envelope-from=manfred@simpligility.com;
 x-software=spfmilter 0.97 http://www.acme.com/software/spfmilter/ with
 libspf2-1.0.0;
Message-ID: <83b053da2b8147291bf8b6f369a4758a.squirrel@www.mosabuam.com>
In-Reply-To: 
 <CAKDUN1tmwTDLY6m=+j8pMHfhnsrOiZ3RAeZwNNFRPCNkXGcx4A@mail.gmail.com>
References: 
    <CAKDUN1tmwTDLY6m=+j8pMHfhnsrOiZ3RAeZwNNFRPCNkXGcx4A@mail.gmail.com>
Date: Thu, 18 Apr 2013 12:41:36 -0400
Subject: Re: The archetype/archetype-catalog mess
From: "Manfred Moser" <manfred@simpligility.com>
To: "Maven Developers List" <dev@maven.apache.org>
Reply-To: manfred@simpligility.com
User-Agent: SquirrelMail/1.4.20-1eapps
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

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