m2 comes with a bunch of build-in packages, but the native ones are not, so you need to activate it as an extension thru user's pom.xml
-D On 6/26/06, Brad Harper <[EMAIL PROTECTED]> wrote:
Oops. I dropped the <extensions> element somehow. Does that element tell maven that a plugin provides new lifecycle functionality? Wouldn't that information be something you'd expect a plugin to reveal about itself ... rather than be declared by a dependent project descriptor? Thanks, Dan. -----Original Message----- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, June 26, 2006 11:36 AM To: Maven Users List Subject: Re: BUILD ERROR using native-maven-plugin: Cannot find lifecycle mapping for packaging: 'lib' I ran the native-maven-plugin/src/it/linkages which as one lib project inthere and have no issue. Did you define <extenstions>true</extensions>? please see the example -Dan On 6/26/06, Brad Harper <[EMAIL PROTECTED]> wrote: > > I've attempted a re-org of modules this morning and now see > > [ERROR] BUILD ERROR > [INFO] ---------------... > [INFO] Cannot find lifecycle mapping for packaging: 'lib'. > Component descriptor cannot be found in the component repository: \ > org.apache.maven.lifecycle.mapping.LifecycleMappingLib. > > ... using Maven 2.0.4 with locally built and installed alpha-1.0 of > native.maven.plugin. > > Brad > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
