You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Anders Hammar <an...@hammar.net> on 2013/04/18 10:22:38 UTC
The archetype/archetype-catalog mess
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
Re: The archetype/archetype-catalog mess
Posted by John Casey <jd...@commonjava.org>.
+1
On 4/18/13 3:22 AM, Anders Hammar wrote:
> 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
>
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
GitHub - http://github.com/jdcasey
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Vincent Latombe <vi...@gmail.com>.
+1
Vincent
2013/4/18 Olivier Lamy <ol...@apache.org>
> sounds good idea.
> +1
>
> 2013/4/18 Anders Hammar <an...@hammar.net>:
> > 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
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: The archetype/archetype-catalog mess
Posted by Olivier Lamy <ol...@apache.org>.
sounds good idea.
+1
2013/4/18 Anders Hammar <an...@hammar.net>:
> 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
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Barrie Treloar <ba...@gmail.com>.
+1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Robert Scholte <rf...@apache.org>.
The archetype for Maven plugins has been enriched with an example of an IT.
That should give developers a start on how to use the maven-invoker-plugin.
There's probably more room for improving documentation on how to make a
kickstart when writing maven-plugins, but that would only be useful if you
could find those docs. Right now the Maven site is a growing list of
hyperlinks, so we also need to rearrange the site.
MRM a different story, I've only used it for plugins where I need to
download a pom.xml from some runtime specified project.
I see opportunities when we integrate MRM into the maven-invoker-plugin,
but I'm not sure if we want a per-test repository. Up until now I've been
able to isolate all mocked artifacts per test. I'd prefer not introduce
extra options if these are not really required.
Robert
Op Sun, 21 Apr 2013 09:08:22 +0200 schreef Stephen Connolly
<st...@gmail.com>:
> On Sunday, 21 April 2013, Barrie Treloar wrote:
>
>> On 21 April 2013 00:50, Robert Scholte
>> <rfscholte@apache.org<javascript:;>>
>> wrote:
>> > @Barrie,
>> >
>> http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.htmlshould
>> > give you a good start.
>> > I'll add something about supported files and how to setup your
>> mockrepo.
>> Is
>> > there something else you'd like to see?
>>
>> Remember its been a while since I've gone searching for the docs so
>> things may be fine now...
>>
>> Its more thank just MRM, its how to use the invoker, why you do things
>> this way, etc, etc. This is especially useful for newbies as
>> integration tests are so useful.
>
>
> I think what you are calling out for is a better guide on how to write
> integration tests for maven plugins on the Maven site.
>
> I am also wondering if it is worth moving MRM into the Maven tree,
> perhaps
> merging with invoker as that would open up some nice synergies, such as
> allowing per-test repositories (or even per part of test, e.g.
> Invoker.properties could have: invoker.mockRepository.2=...)
>
> -Stephen
>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
>> For additional commands, e-mail: dev-help@maven.apache.org
>> <javascript:;>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Stephen Connolly <st...@gmail.com>.
On Sunday, 21 April 2013, Barrie Treloar wrote:
> On 21 April 2013 00:50, Robert Scholte <rfscholte@apache.org<javascript:;>>
> wrote:
> > @Barrie,
> > http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.htmlshould
> > give you a good start.
> > I'll add something about supported files and how to setup your mockrepo.
> Is
> > there something else you'd like to see?
>
> Remember its been a while since I've gone searching for the docs so
> things may be fine now...
>
> Its more thank just MRM, its how to use the invoker, why you do things
> this way, etc, etc. This is especially useful for newbies as
> integration tests are so useful.
I think what you are calling out for is a better guide on how to write
integration tests for maven plugins on the Maven site.
I am also wondering if it is worth moving MRM into the Maven tree, perhaps
merging with invoker as that would open up some nice synergies, such as
allowing per-test repositories (or even per part of test, e.g.
Invoker.properties could have: invoker.mockRepository.2=...)
-Stephen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
>
>
--
Sent from my phone
Re: The archetype/archetype-catalog mess
Posted by Barrie Treloar <ba...@gmail.com>.
On 21 April 2013 00:50, Robert Scholte <rf...@apache.org> wrote:
> @Barrie,
> http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.html should
> give you a good start.
> I'll add something about supported files and how to setup your mockrepo. Is
> there something else you'd like to see?
Remember its been a while since I've gone searching for the docs so
things may be fine now...
Its more thank just MRM, its how to use the invoker, why you do things
this way, etc, etc. This is especially useful for newbies as
integration tests are so useful.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Anders Hammar <an...@hammar.net>.
Thanks Robert!
/Anders
On Wed, May 15, 2013 at 12:35 PM, Robert Scholte <rf...@apache.org>wrote:
> @Anders,
>
> I've just done a huge commit for MMOCKRM-10, so you could give it a try.
> For the catalog, it expects a archetype-catalog.xml in the root of the
> repository, just as the real world.
>
> Robert
>
>
> Op Sat, 20 Apr 2013 17:20:04 +0200 schreef Robert Scholte <
> rfscholte@apache.org>:
>
>
> @Anders, I'm almost ready with MMOCKRM-10, but I'm hitting a chicken-egg
>> problem: we both need to write IT's with a snapshot version of MRM and with
>> the adjusted maven-archetype-plugin.
>> I'll try to cover most with unittests and let's see what we want to
>> release first.
>>
>> @Barrie, http://mojo.codehaus.org/mrm-**maven-plugin/examples/invoker-**
>> tests.html<http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.html>should give you a good start.
>> I'll add something about supported files and how to setup your mockrepo.
>> Is there something else you'd like to see?
>>
>> Robert
>>
>> Op Fri, 19 Apr 2013 00:17:07 +0200 schreef Barrie Treloar <
>> baerrach@gmail.com>:
>>
>> On 19 April 2013 03:56, Anders Hammar <an...@hammar.net> wrote:
>>>
>>>> I can help with MMOCKRM-10 and its integration for the ITs, I've done it
>>>>> several times.
>>>>>
>>>>>
>>>> That would be awesome. It's actually what has made me postpone this for
>>>> a
>>>> while.
>>>>
>>>
>>> If you could update any docs with this information that would be helpful
>>> too.
>>>
>>> I haven't look at IT tests since there were at least three different
>>> choices...
>>> and all of them were black magic.
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: The archetype/archetype-catalog mess
Posted by Robert Scholte <rf...@apache.org>.
@Anders,
I've just done a huge commit for MMOCKRM-10, so you could give it a try.
For the catalog, it expects a archetype-catalog.xml in the root of the
repository, just as the real world.
Robert
Op Sat, 20 Apr 2013 17:20:04 +0200 schreef Robert Scholte
<rf...@apache.org>:
> @Anders, I'm almost ready with MMOCKRM-10, but I'm hitting a chicken-egg
> problem: we both need to write IT's with a snapshot version of MRM and
> with the adjusted maven-archetype-plugin.
> I'll try to cover most with unittests and let's see what we want to
> release first.
>
> @Barrie,
> http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.html
> should give you a good start.
> I'll add something about supported files and how to setup your mockrepo.
> Is there something else you'd like to see?
>
> Robert
>
> Op Fri, 19 Apr 2013 00:17:07 +0200 schreef Barrie Treloar
> <ba...@gmail.com>:
>
>> On 19 April 2013 03:56, Anders Hammar <an...@hammar.net> wrote:
>>>> I can help with MMOCKRM-10 and its integration for the ITs, I've done
>>>> it
>>>> several times.
>>>>
>>>
>>> That would be awesome. It's actually what has made me postpone this
>>> for a
>>> while.
>>
>> If you could update any docs with this information that would be
>> helpful too.
>>
>> I haven't look at IT tests since there were at least three different
>> choices...
>> and all of them were black magic.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Robert Scholte <rf...@apache.org>.
@Anders, I'm almost ready with MMOCKRM-10, but I'm hitting a chicken-egg
problem: we both need to write IT's with a snapshot version of MRM and
with the adjusted maven-archetype-plugin.
I'll try to cover most with unittests and let's see what we want to
release first.
@Barrie,
http://mojo.codehaus.org/mrm-maven-plugin/examples/invoker-tests.html
should give you a good start.
I'll add something about supported files and how to setup your mockrepo.
Is there something else you'd like to see?
Robert
Op Fri, 19 Apr 2013 00:17:07 +0200 schreef Barrie Treloar
<ba...@gmail.com>:
> On 19 April 2013 03:56, Anders Hammar <an...@hammar.net> wrote:
>>> I can help with MMOCKRM-10 and its integration for the ITs, I've done
>>> it
>>> several times.
>>>
>>
>> That would be awesome. It's actually what has made me postpone this for
>> a
>> while.
>
> If you could update any docs with this information that would be helpful
> too.
>
> I haven't look at IT tests since there were at least three different
> choices...
> and all of them were black magic.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Barrie Treloar <ba...@gmail.com>.
On 19 April 2013 03:56, Anders Hammar <an...@hammar.net> wrote:
>> I can help with MMOCKRM-10 and its integration for the ITs, I've done it
>> several times.
>>
>
> That would be awesome. It's actually what has made me postpone this for a
> while.
If you could update any docs with this information that would be helpful too.
I haven't look at IT tests since there were at least three different choices...
and all of them were black magic.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Anders Hammar <an...@hammar.net>.
> I can help with MMOCKRM-10 and its integration for the ITs, I've done it
> several times.
>
That would be awesome. It's actually what has made me postpone this for a
while.
/Anders
>
> Robert
>
> Op Thu, 18 Apr 2013 18:41:36 +0200 schreef Manfred Moser <
> manfred@simpligility.com>:
>
>
> 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<de...@maven.apache.org>
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<de...@maven.apache.org>
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: The archetype/archetype-catalog mess
Posted by Robert Scholte <rf...@apache.org>.
+1
I can help with MMOCKRM-10 and its integration for the ITs, I've done it
several times.
Robert
Op Thu, 18 Apr 2013 18:41:36 +0200 schreef Manfred Moser
<ma...@simpligility.com>:
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Baptiste MATHUS <bm...@batmat.net>.
+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 <an...@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 !
Re: The archetype/archetype-catalog mess
Posted by Brett Porter <br...@porterclan.net>.
On 19/04/2013, at 4:29 AM, Anders Hammar <an...@hammar.net> wrote:
> 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?
This should be fine, just bearing in mind that you need to be extra careful about <prerequisites> so that Maven 2.2.1 users don't pull the latest and get a broken archetype system. A bad version was released once and much confusion reigned.
You will need to maintain some level of compatibility with old archetypes, if it comes to that too.
+1 overall, this particular thing has been quite annoying in the past, thanks for picking it up!
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Manfred Moser <ma...@simpligility.com>.
Moving fast would certainly different... but very good imho!
manfred
> 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
> <ma...@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
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: The archetype/archetype-catalog mess
Posted by Anders Hammar <an...@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 <ma...@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
>
>
Re: The archetype/archetype-catalog mess
Posted by Manfred Moser <ma...@simpligility.com>.
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
Re: The archetype/archetype-catalog mess
Posted by Hervé BOUTEMY <he...@free.fr>.
+1
Regards,
Hervé
Le jeudi 18 avril 2013 10:22:38 Anders Hammar a écrit :
> 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