2007/4/17, Jason van Zyl <[EMAIL PROTECTED]>:
On 17 Apr 07, at 2:51 PM 17 Apr 07, Raphaël Piéroni wrote:
> Hi,
>
> With the archetypeng stuff, i think i have reached
> a point in which i need advice.
>
> For what i can see, the current code seems useable.
>
Can you:
1) Create an archetype from an existing project
Yep but only for non multi project archetype.
Only pom, src/main, src/test src/site are resolved
2) Have a way to deploy the Archetypes
archetypes are deployed as 'normal' maven plugins
because plugin metadata are needed.
So they are deployed as usual.
3) Can use the deployed Archetype to generate a project
Yep for archetypes using the current proposition descriptor
and using the actual descriptor
If you can do that then I would consider it usable.
Please have a try. There is sample doco at mojo.codehaus.org/maven-archetypeng
> I am currently refactoring the proposed descriptor.
> This change will be incompatible with the current
> proposition, which mimics and enchance the
> actual behaviour.
>
If you just want to try and new descriptor and then return to being
compatible then you don't need to branch. The old code is being used
anyway.
Not sure I understand why you need to create a branch.
I think i don't have well explained myself.
1. I call the 'actual descriptor' the descriptor of maven-archetype-plugin
2. I call the 'current proposition descriptor' the descriptor that is
currently in the SCM at mojo
3. I call the 'new descriptor' the descriptor i currently am working on.
When i talked about incompatibilities, i meant between 2 and 3.
1 remain supported as it is currently in the code at mojo.
I realise now what i need is to define 2 descriptor in the proposition
and let the generation process guess which of 1, 2 or 3 is used and
also let the creation process to ask for which of 2 or 3 is required
(or maybe let only 3)
The branch i need is not in the SCM but is in the code by refining the design.
Thanks for making me realised that.
The only questions that remain to me are:
- an improvement i can't do is to have archetypeGroups defined as
pluginGroup in the settings
- another improvement is to generate and deploy specific metadata
similar to plugin ones
- have a new packaging named 'maven-archetype' which use the modified deployment
Regards,
Raphaël
Jason.
> I think i need to reprensent this changing in the SCM,
> but i can't figure the right way:
>
> a) create a branch in the mojo repository (but the current code is in
> the sandbox)
> b) tag by hand a 0.1-alpha-1 version (with lazy concensus vote) and
> stay in the sandbox
> c) use the release plugin to release as version (idem vote) and stay
> in the sandbox
>
> I dislike c, and have a light preference for b.
>
> Thanks in advance for any answer.
>
> Regards,
>
> Raphaël
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
