Sure, will try to keep up.
I had a year ago (while doing nexus-archetype-plugin) a discussion with
Raphael Pieroni (sorry for ASCII-zation of his name!), is he "The Man" to
ping?
Thanks,
~t~
On Sun, Nov 21, 2010 at 6:01 PM, Hervé BOUTEMY wrote:
> Le jeudi 18 novembre 2010, Brett Porter a écrit
Le jeudi 18 novembre 2010, Brett Porter a écrit :
> > Could please someone (Herve?) review it and apply?
>
> You can actually commit it yourself if you'd like (and then perhaps for
> specific review if you are unsure) - lazy consensus and relying on version
> control are fine :)
+1, even if I'm a
Hi,
glad you like it :)
Just to clear up: the initial reason for this was to make integration of
archetype-based solutions easier into non-maven apps. For example, for
nexus-archetype-plugin, I really needed the model _only_, nothing else, so I
"stole" the modello mdo file of archetype-catalog (a
On 19/11/2010, at 9:23 AM, Tamás Cservenák wrote:
> Hi there,
>
> I attached the patch for solving
> http://jira.codehaus.org/browse/ARCHETYPE-303 "Externalize Archetype Catalog
> model into separate module" issue. This patch externalizes (moves out into
> separate module) each modello model, le
Hi there,
I attached the patch for solving
http://jira.codehaus.org/browse/ARCHETYPE-303 "Externalize Archetype Catalog
model into separate module" issue. This patch externalizes (moves out into
separate module) each modello model, leaving just the "old" 1.x
archetype.mdo in archetype-commons.
Co
