baerrach wrote:
>
> See http://jira.codehaus.org/browse/MECLIPSE-37
> There doesn't seem to be anything on the mailing lists to help with
> this problem.
>
This is an interesting problem.
I don't see any way to fix this other than changing Maven itself,
unfortunately, but I think Arnaud's idea about the lifecycle is a good one.
What about a "generate" lifecycle that just does all the generation phases
(ie, the ones you've listed), and ends with a "generate" phase. Someone
could bind eclipse/idea/whatever to that, and run "mvn generate" from the
command line.
We might need to hash out the details, but I think it's worth trying it to
see if it works for your use case first to see if it is worthwhile pursuing
further - you could do this on the maven-2.1.x branch and add it to the
maven-core components.xml file.
Cheers,
Brett
--
View this message in context:
http://www.nabble.com/MECLIPSE-37-creating-a-new-custom-lifecycle-for-m-eclipse-p-tp20846234p20958158.html
Sent from the Maven Developers mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
