RE: Error looking up lifecycle mapping to retrieve optional mojos
Hi Eric, Dan, Thanks a lot for your support! I was thinking that I am too stupid to get this straigt. = I will try the workaround as proposed by Eric = I will open a JIRA for maven-plugin-plugin I agree, plexus documentation is bad - even with the book, there could be a lot more material. Andreas -Original Message- From: ext dan tran [mailto:[EMAIL PROTECTED] Sent: 10 June, 2006 18:44 To: Maven Users List Subject: Re: Error looking up lifecycle mapping to retrieve optional mojos native-maven-plugin experience the same thing, sound like a bug Please file a JIRA Eric, where do have the work around? your plugin's pom? or the the project that use it? -D On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-applica tion Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration prefixruby/prefix /configuration dependencies dependency groupIdorg.codehaus.mojo/groupId artifactIdrubyscript-maven-plugin/artifactId version1.0-alpha-3-SNAPSHOT/version /dependency /dependencies /plugin /plugins Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:440) at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona lMojosForLifecycle(Default LifecycleExecutor.java:1106) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc leForPackaging(DefaultLife cycleExecutor.java:994
RE: Error looking up lifecycle mapping to retrieve optional mojos
On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote: Hi, I believe the workaround is unneccesary. You just need to specify extensionstrue/extensions in the plugin setion in the depending pom. -- Kenney Hi Eric, Dan, Thanks a lot for your support! I was thinking that I am too stupid to get this straigt. = I will try the workaround as proposed by Eric = I will open a JIRA for maven-plugin-plugin I agree, plexus documentation is bad - even with the book, there could be a lot more material. Andreas -Original Message- From: ext dan tran [mailto:[EMAIL PROTECTED] Sent: 10 June, 2006 18:44 To: Maven Users List Subject: Re: Error looking up lifecycle mapping to retrieve optional mojos native-maven-plugin experience the same thing, sound like a bug Please file a JIRA Eric, where do have the work around? your plugin's pom? or the the project that use it? -D On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-applica tion Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration prefixruby/prefix /configuration dependencies dependency groupIdorg.codehaus.mojo/groupId artifactIdrubyscript-maven-plugin/artifactId version1.0-alpha-3-SNAPSHOT/version /dependency /dependencies /plugin /plugins Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:440) at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120
Re: Error looking up lifecycle mapping to retrieve optional mojos
Kenney, The annoying warning is there even with extensionstrue/extensions. BTW, lifecycle extension will not work at all if you dont have extensionstrue/extensions specified thou -D On 6/12/06, Kenney Westerhof [EMAIL PROTECTED] wrote: On Mon, 12 Jun 2006 [EMAIL PROTECTED] wrote: Hi, I believe the workaround is unneccesary. You just need to specify extensionstrue/extensions in the plugin setion in the depending pom. -- Kenney Hi Eric, Dan, Thanks a lot for your support! I was thinking that I am too stupid to get this straigt. = I will try the workaround as proposed by Eric = I will open a JIRA for maven-plugin-plugin I agree, plexus documentation is bad - even with the book, there could be a lot more material. Andreas -Original Message- From: ext dan tran [mailto:[EMAIL PROTECTED] Sent: 10 June, 2006 18:44 To: Maven Users List Subject: Re: Error looking up lifecycle mapping to retrieve optional mojos native-maven-plugin experience the same thing, sound like a bug Please file a JIRA Eric, where do have the work around? your plugin's pom? or the the project that use it? -D On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-applica tion Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration prefixruby/prefix /configuration dependencies dependency groupIdorg.codehaus.mojo/groupId artifactIdrubyscript-maven-plugin/artifactId version1.0-alpha-3-SNAPSHOT/version /dependency /dependencies /plugin /plugins Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application
Re: Error looking up lifecycle mapping to retrieve optional mojos
Unfortunately, the project that uses it. That's why I was forced to create a parent POM which contains the build/plugins configurations -- to save users from having to add it manually in their own POMs. If it could be added in my own plugin, that would be great. Eric On 6/10/06, dan tran [EMAIL PROTECTED] wrote: native-maven-plugin experience the same thing, sound like a bug Please file a JIRA Eric, where do have the work around? your plugin's pom? or the the project that use it? -D On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-application Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration prefixruby/prefix /configuration dependencies dependency groupIdorg.codehaus.mojo/groupId artifactIdrubyscript-maven-plugin/artifactId version1.0-alpha-3-SNAPSHOT/version /dependency /dependencies /plugin /plugins Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:440) at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona lMojosForLifecycle(Default LifecycleExecutor.java:1106) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc leForPackaging(DefaultLife cycleExecutor.java:994) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi fecycleMappings(DefaultLif ecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor. java:453) at
RE: Error looking up lifecycle mapping to retrieve optional mojos
Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:440) at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona lMojosForLifecycle(Default LifecycleExecutor.java:1106) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc leForPackaging(DefaultLife cycleExecutor.java:994) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi fecycleMappings(DefaultLif ecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor. java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal AndHandleFailures(DefaultL ifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTask Segments(DefaultLifecycleE xecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Def aultLifecycleExecutor.java :140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccesso rImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho dAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) My plugins component.xml: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hinttigerstripe-application/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifec ycleMapping/implementation configuration phases generate-sourcesossj.jsr264:maven-tigerstripe-plugin:tigerstr ipe-generate/generate-sources packageorg.apache.maven.plugins:maven-source-plugin:jar/package installorg.apache.maven.plugins:maven-install-plugin:install /install /phases /configuration
Re: Error looking up lifecycle mapping to retrieve optional mojos
Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-application Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration prefixruby/prefix /configuration dependencies dependency groupIdorg.codehaus.mojo/groupId artifactIdrubyscript-maven-plugin/artifactId version1.0-alpha-3-SNAPSHOT/version /dependency /dependencies /plugin /plugins Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:440) at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona lMojosForLifecycle(Default LifecycleExecutor.java:1106) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc leForPackaging(DefaultLife cycleExecutor.java:994) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi fecycleMappings(DefaultLif ecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor. java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal AndHandleFailures(DefaultL ifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTask Segments(DefaultLifecycleE xecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Def aultLifecycleExecutor.java :140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccesso rImpl.java:39) at
Re: Error looking up lifecycle mapping to retrieve optional mojos
native-maven-plugin experience the same thing, sound like a bug Please file a JIRA Eric, where do have the work around? your plugin's pom? or the the project that use it? -D On 6/10/06, Eric Redmond [EMAIL PROTECTED] wrote: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigerstripe-application Component role-hints in Plexus are tacked onto the end of the role name, and loaded like a role (someone correct me if I'm wrong about this... good Plexus documentation is nonexistant). The problem is that your classloader isn't finding your component.xml file, and so when it tries to load your tigerstripe-application packaging role-hint, its not there. You have to tell the maven-plugin-plugin about your project. What I ended up having to do was add my plugin as a dependency of maven-plugin-plugin in the POM that was using it: plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration prefixruby/prefix /configuration dependencies dependency groupIdorg.codehaus.mojo/groupId artifactIdrubyscript-maven-plugin/artifactId version1.0-alpha-3-SNAPSHOT/version /dependency /dependencies /plugin /plugins Its kind of ugly, so I created a parent that all plugin projects may inherit from. It works. If you find a better way to make the plugin-plugin find your components, however, please be good enough to post it. Eric On 6/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Has somebody else also had this error? What can I do about it? Thanks, _ ___ _ //\ndreas.[|-bbert-[]/arroum(a)[|\|okia.com `-` Andreas Ebbert-Karroum Senior Software Design Engineer Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-9412-3838 Heltorfer Straße 1, 40472 Düsseldorf, Germany -- This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/ -- -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:440) at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona lMojosForLifecycle(Default LifecycleExecutor.java:1106) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc leForPackaging(DefaultLife cycleExecutor.java:994) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi fecycleMappings(DefaultLif ecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor. java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal AndHandleFailures(DefaultL ifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTask Segments(DefaultLifecycleE xecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Def aultLifecycleExecutor.java :140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
RE: Error looking up lifecycle mapping to retrieve optional mojos
Does somebody have a clue, what's going on here? Can I safely ignore the debug warning? I have no idea what it is trying to tell me... Thanks, Andreas -Original Message- From: ext [EMAIL PROTECTED] e.org [mailto:[EMAIL PROTECTED] en.apache.org] Sent: 08 June, 2006 01:09 To: users@maven.apache.org Subject: Error looking up lifecycle mapping to retrieve optional mojos Hi, I've defined my own plugin (with the maven-plugin-tools-ant plugin) with it's own lifecycle and artifact handler. when I now try to use the plugin in another project, it works fine, but I'm getting this debug warning - and I have no clue, what it is about - can it be fixed, and if yes, how? [DEBUG] Error looking up lifecycle mapping to retrieve optional mojos. Lifecycle ID: default. Error: Component descriptor cannot be found in the component repository: org.apache.maven.lifecycle.mappin g.LifecycleMappingtigerstripe-application. org.codehaus.plexus.component.repository.exception.ComponentLoo kupException: Component descriptor ca nnot be found in the component repository: org.apache.maven.lifecycle.mapping.LifecycleMappingtigers tripe-application. at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:323) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexus Container.java:440) at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findOptiona lMojosForLifecycle(Default LifecycleExecutor.java:1106) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecyc leForPackaging(DefaultLife cycleExecutor.java:994) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLi fecycleMappings(DefaultLif ecycleExecutor.java:975) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultLifecycleExecutor. java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal AndHandleFailures(DefaultL ifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTask Segments(DefaultLifecycleE xecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Def aultLifecycleExecutor.java :140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccesso rImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMetho dAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) My plugins component.xml: component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hinttigerstripe-application/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifec ycleMapping/implementation configuration phases generate-sourcesossj.jsr264:maven-tigerstripe-plugin:tigerstr ipe-generate/generate-sources packageorg.apache.maven.plugins:maven-source-plugin:jar/package installorg.apache.maven.plugins:maven-install-plugin:install /install /phases /configuration /component component roleorg.apache.maven.artifact.handler.ArtifactHandler/role role-hinttigerstripe-application/role-hint implementationorg.apache.maven.artifact.handler.DefaultArtifa ctHandler/implementation configuration extensionjar/extension typetigerstripe-application/type /configuration /component /components /component-set My plugins POM: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdossj.jsr264/groupId artifactIdmaven-tigerstripe-plugin/artifactId packagingmaven-plugin/packaging nameMaven Wrapper for ant build script to use Tigerstripe Workbench/name
