Kenny thanks for the help, however I am not sure we're on the right track yet
> You don't need to modify maven-core/META-INF/components.xml. That only > defines the global lifecycle. As far as I can tell it also defines other lifecycles such as the plexus-application lifecycle, which is where I am getting my clues from. BTW I mistyped the file name, the correct full path is maven-core/src/main/resources/META-INF/plexus/components.xml as you state below. > > 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'. > No I believe I have the role-hint correctly stated as 'eclipse-plugin' > 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). This is where I have been looking. As far as I can tell, the problem is that the packaging hints are only looked for from the core components, so even when I have those defined in my plugin, it is not inspected until it is too late Matthew --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
