Jason van Zyl <[EMAIL PROTECTED]> writes:

> On 2 Aug 07, at 9:22 AM 2 Aug 07, Arnaud Bailly wrote:
>
>> "Sebastien Brunot" <[EMAIL PROTECTED]> writes:
>>
>>> Am I asking the question to the good mailing list ? Should it be
>>> asked
>>> to the user mailing list instead ?
>>>
>>
>> Sure, this is the right ML.
>> Part of the answer may be here:
>> http://jira.codehaus.org/browse/MNG-1950
>>
>> In short: you can't without hacking maven sources :-) Or maybe that
>> has changed recently....
>>

>
> To make a new lifecycle say for a custom component? We have a
> lifecycle for archetypes now, and projects like XWiki have their own
> custom lifecycles. Doesn't require changing the sources. Not sure in
> what context you mean it requires hacking the sources but many people
> have made custom lifecycles.
>

Pretty sure you better than me, so you must be right. 

I inferred this answer while browsing the referred Jira issues,
various questions/answers  seemed to distinguish 2 cases:
 - the easy one: I want to create a custom *mapping* for the maven
   lifecycle, eg. like what is done in maven-archetype: Need to create
   a component.xml for plexus, with mapping for 
 - the hard one (at least it seems so): I want to define a custom
   *lifecycle*, that is have my own phases executed, along with their
   mapping. 

But as I said, I would be happy to be corrected, maybe with some
helpful pointer to example.

Regards,
-- 
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to