On Tue, 5 Jul 2005, Rafal Krzewski wrote: I'm not a developer, but I can give you some pointers:
You don't need to modify maven-core/META-INF/components.xml. That only defines the global lifecycle. The exception you got is because your copy probably specified the role-hint plexus-application. That's where it should say 'eclipse-plugin'. I guess you read http://maven.apache.org/maven2/lifecycle.html ? Btw, you probably meant to have an 'eclipse' packaging. Then the role-hint should be 'eclipse'. As far as I understand, you can only bind mojo's to existing lifecycle phases. That means that a 'custom' lifecycle is merely a copy of the 'root' lifecycle (in maven-core/META-INF/components.xml) with different mojo bindings to each phase. So in summary: the phases are fixed; what you bind to them isn't. You might find some examples in the different packaging systems: maven-core/src/main/resources/META-INF/plexus/components.xml. Search for 'maven-plugin' (it's a packaging). > Matthew Pryor wrote: > > > So I can see how a custom lifecycle is defined & implemented, but clearly > > having to modify maven-core/META-INF/components.xml to get my > > lifecycle/packaging registered is BAD > > Definetely. > > Since the developers didn't pick up the discussion, maybe you should > file a Jira issue to get their attention? > > Rafal > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
