Stéphane, Richard, Piotr et al
Pls help :-) I still have a lifecycle problem.. with
<packaging>par</packaging> !!!
Downloaded, compiled, packaged and installed par and ejb3 plugins from
sandbox. Local repository shows
.m2\repository\org\apache\maven\plugins\maven-par-plugin\2.1-SNAPSHOT
...
<project>
<parent>
<artifactId>maven-plugin-parent</artifactId>
<groupId>org.apache.maven.plugins</groupId>
<version>2.0</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>maven-par-plugin</artifactId>
<packaging>maven-plugin</packaging>
<name>Maven Par plugin</name>
<version>2.1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-project</artifactId>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-archiver</artifactId>
<version>2.0</version>
</dependency>
</dependencies>
<distributionManagement>
<status>deployed</status>
</distributionManagement>
</project>
....
and
.....
<project>
<parent>
<artifactId>maven-plugin-parent</artifactId>
<groupId>org.apache.maven.plugins</groupId>
<version>2.0</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>maven-ejb3-plugin</artifactId>
<packaging>maven-plugin</packaging>
<name>Maven EJB3 plugin</name>
<version>2.1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-project</artifactId>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-archiver</artifactId>
<version>2.0</version>
</dependency>
</dependencies>
<distributionManagement>
<status>deployed</status>
</distributionManagement>
</project>
...
maven-par-plugin-2.1-SNAPSHOT.jar has a componets.xml of:
...
<component-set>
<components>
<component>
<role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role>
<role-hint>par</role-hint>
<implementation>org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping</implementation>
<configuration>
<lifecycles>
<lifecycle>
<id>default</id>
<!-- START SNIPPET: par-lifecycle -->
<phases>
<process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
<compile>org.apache.maven.plugins:maven-compiler-plugin:compile</compile>
<process-test-resources>
org.apache.maven.plugins:maven-resources-plugin:testResources</process-test-resources>
<test-compile>org.apache.maven.plugins:maven-compiler-plugin:testCompile</test-compile>
<test>org.apache.maven.plugins:maven-surefire-plugin:test</test>
<package>
org.apache.maven.plugins:maven-par-plugin:par
</package>
<install>org.apache.maven.plugins:maven-install-plugin:install</install>
<deploy>org.apache.maven.plugins:maven-deploy-plugin:deploy</deploy>
</phases>
<!-- END SNIPPET: par-lifecycle -->
</lifecycle>
</lifecycles>
</configuration>
</component>
</components>
</component-set>
...
WHICH I THINK IS THE FIXED VERSION (?)
My top level POM only has the local repos listed:
...
<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";>
<modelVersion>4.0.0</modelVersion>
<groupId>uk.co.acora</groupId>
<artifactId>jewel</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>
<repositories>
<repository>
<id>local</id>
<name>Locolhost Maven Repository</name>
<url>file:C:/Documents and Settings/Administrator/.m2/repository</url>
<layout>default</layout>
</repository>
<!--
<repository>
<id>central</id>
<name>Maven Repository Switchboard</name>
<url>http://repo1.maven.org/maven2</url>
<layout>default</layout>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
-->
</repositories>
<modules>
<module>jewel-common</module>
<module>jewel-data-access</module>
<module>jewel-business</module>
<module>jewel-web</module>
<module>jewel-jboss-ear</module>
</modules>
</project>
...
and the <module>jewel-data-access</module> has a 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";>
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>uk.co.acora</groupId>
<artifactId>jewel</artifactId>
<version>1.0-SNAPSHOT</version>
</parent>
<groupId>uk.co.acora</groupId>
<artifactId>jewel-data-access</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>par</packaging>
<dependencies>
<dependency>
<groupId>javax.persistence</groupId>
<artifactId>ejb</artifactId>
<version>3.0-public_review</version>
<scope>compile</scope>
</dependency>
</dependencies>
</project>
BUT trying to compile from either the top level or data access module
results in ERROR:
...
E:\development\projects\jewel\jewel-data-access>mvn -v
Maven version: 2.0.1-SNAPSHOT
E:\development\projects\jewel\jewel-data-access>mvn -e compile
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed - uk.co.acora:jewel-data-access:par:1.0-SNAPSHOT
[INFO] task-segment: [compile]
[INFO]
----------------------------------------------------------------------------
[ERROR] Nonexistent component:
org.apache.maven.lifecycle.mapping.LifecycleMappingp
ar
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] Cannot find lifecycle mapping for packaging: 'par'.
Component descriptor cannot be found in the component repository:
org.apache.maven.
lifecycle.mapping.LifecycleMappingpar.
[INFO]
----------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot find
lifecycle mappi
ng for packaging: 'par'.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findMappingsForLifec
ycle(DefaultLifecycleExecutor.java:945)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPack
aging(DefaultLifecycleExecutor.java:879)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
ppings(DefaultLifecycleExecutor.java:862)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:447)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:137)
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:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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)
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupExcept
ion: Component descriptor cannot be found in the component repository:
org.apache.m
aven.lifecycle.mapping.LifecycleMappingpar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:319)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:436)
at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findMappingsForLifec
ycle(DefaultLifecycleExecutor.java:938)
... 17 more
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Oct 05 23:38:46 BST 2005
[INFO] Final Memory: 1M/2M
[INFO]
----------------------------------------------------------------------------
Similalrly from the master/parent project level
E:\development\projects\jewel
E:\development\projects\jewel>mvn -v
Maven version: 2.0.1-SNAPSHOT
E:\development\projects\jewel>mvn -e compile
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - uk.co.acora:jewel:pom:1.0-SNAPSHOT
[INFO] Unnamed - uk.co.acora:jewel-common:jar:1.0-SNAPSHOT
[INFO] Unnamed - uk.co.acora:jewel-data-access:par:1.0-SNAPSHOT
[INFO] Unnamed - uk.co.acora:jewel-business:ejb3:1.0-SNAPSHOT
[INFO] Unnamed - uk.co.acora:jewel-web:war:1.0-SNAPSHOT
[INFO] Unnamed - uk.co.acora:jewel-jboss-ear:ear:1.0-SNAPSHOT
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed - uk.co.acora:jewel:pom:1.0-SNAPSHOT
[INFO] task-segment: [compile]
[INFO]
----------------------------------------------------------------------------
[INFO] No goals needed for project - skipping
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed - uk.co.acora:jewel-common:jar:1.0-SNAPSHOT
[INFO] task-segment: [compile]
[INFO]
----------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 1 source file to
E:\development\projects\jewel\jewel-common\target\classe
s
[INFO]
----------------------------------------------------------------------------
[INFO] Building Unnamed - uk.co.acora:jewel-data-access:par:1.0-SNAPSHOT
[INFO] task-segment: [compile]
[INFO]
----------------------------------------------------------------------------
[ERROR] Nonexistent component:
org.apache.maven.lifecycle.mapping.LifecycleMappingp
ar
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] Cannot find lifecycle mapping for packaging: 'par'.
Component descriptor cannot be found in the component repository:
org.apache.maven.
lifecycle.mapping.LifecycleMappingpar.
[INFO]
----------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Cannot find
lifecycle mappi
ng for packaging: 'par'.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findMappingsForLifec
ycle(DefaultLifecycleExecutor.java:945)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPack
aging(DefaultLifecycleExecutor.java:879)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
ppings(DefaultLifecycleExecutor.java:862)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:447)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:301)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:268)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:137)
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:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.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)
Caused by:
org.codehaus.plexus.component.repository.exception.ComponentLookupExcept
ion: Component descriptor cannot be found in the component repository:
org.apache.m
aven.lifecycle.mapping.LifecycleMappingpar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:319)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer
.java:436)
at org.apache.maven.execution.MavenSession.lookup(MavenSession.java:120)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findMappingsForLifec
ycle(DefaultLifecycleExecutor.java:938)
... 17 more
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Wed Oct 05 23:43:53 BST 2005
[INFO] Final Memory: 2M/9M
[INFO]
----------------------------------------------------------------------------
I am new to maven so might be missing something obvious. Surely, the
rest of the community must be trying or thinking about
a multi-module project with ejb3/par packaging, any good / complete
examples out there with 'Instructions for Dummies' !?
Many thanks in advance.
Regards
Cameron
On 15/11/05, cameron clarke <[EMAIL PROTECTED]> wrote:
>
> Stéphane,
>
> thks v.much I shall keep my eye out for this later today and pull down the
> latest code in subversion tonight.
> I'm new to maven and assume that mvn -cpu compile
> in the local directories I have for the maven2 source:
>
> /maven-components/maven-plugins/maven-ejb3-plugin
> and
> /maven-components/maven-plugins/maven-par-plugin
>
> followed by mvn package and install to my local repository will be enough to
> expose this new functionality for my
>
> local development projects. Then for one of these local development projects
> with <packaging>par</packaging> and/or <packaging>ejb3</packaging> change the
> pom.xml to use my local repository not central
>
> and that it !? ....:-)
>
> thks again
> Rgds
> Cameron
>
> Cameron,
>
> I need to commit the EJB3 and PAR plugins in the sandboxk. Then you'll have
> to install them locally till an official release.
>
>
> Let me know if you need further details.
>
> Hope it helps,
> Stéphane
>
>
> On 11/14/05, cameron clarke <[EMAIL PROTECTED]> wrote:
> >
> > :-( oh my understanding of the commentary in
>
> >
> > http://jira.codehaus.org/secure/Dashboard.jspa?os_destination=%2Fbrowse%2FMNG-699
> >
> > and bleeding edge build from svn source with the addition of
>
> > JarMojo.java-patch.zip and maven2-ejb3-support.zip enabled this
> > functionality although it's not there out of the box with version 2.
> >
> >
> > On 14/11/05, cameron clarke <
> [EMAIL PROTECTED]> wrote:
> > >
> > > ejb3 and par packaging types.
> > > when I attempt to build a multi-module I get the following error:
> > >
> > > [INFO] Building Unnamed -
> uk.co.abc:abc-data-access:par:1.0-SNAPSHOT
> > > [INFO] task-segment: [compile]
> > > [INFO]
> > >
> > ----------------------------------------------------------------------------
> > > [ERROR] Nonexistent component:
>
> > > org.apache.maven.lifecycle.mapping.LifecycleMappingpar
> > > [INFO]
> > >
> > ----------------------------------------------------------------------------
> > >
> > > [ERROR] BUILD ERROR
>
> > > [INFO]
> > >
> > ----------------------------------------------------------------------------
> > > [INFO] Cannot find lifecycle mapping for packaging: 'par'.
> > > Component descriptor cannot be found in the component repository:
>
> > > org.apache.maven.life
> > > cycle.mapping.LifecycleMappingpar.
> > > [INFO]
> > >
> > ----------------------------------------------------------------------------
> > > [INFO] Trace
>
> > > org.apache.maven.lifecycle.LifecycleExecutionException: Cannot find
> > > lifecycle mapping f
> > > or packaging: 'par'.
> > > at
> > >
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.findMappingsForLifecycle
>
> > > (DefaultLifecycleExecutor.java:945)
> > > at
> > >
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackagin
> > > g(DefaultLifecycleExecutor.java:879)
> > > at
>
> > >
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappin
> > > gs(DefaultLifecycleExecutor.java:862)
> > > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
>
> > (DefaultLifec
> > > ycleExecutor.java:447)
> > > at
> > >
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFail
> > > ures(DefaultLifecycleExecutor.java:301)
>
> > > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
> > (Defa
> > > ultLifecycleExecutor.java:268)
> > > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
>
> > > (DefaultLifecycle
> > > Executor.java:137)
> > > 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:249)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > > NativeMethodAccessorImpl.java
> :39
> > > )
> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke
> > > (DelegatingMethodAccessorImpl
> > > .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)
> > > Caused by:
> > >
> > org.codehaus.plexus.component.repository.exception.ComponentLookupException
> > > :
>
> > > Component descriptor cannot be found in the component repository:
> > > org.apache.maven.lif
> > > ecycle.mapping.LifecycleMappingpar.
> > > at org.codehaus.plexus.DefaultPlexusContainer.lookup
> (
> > > DefaultPlexusContainer.jav
> > > a:319)
> > > at org.codehaus.plexus.DefaultPlexusContainer.lookup (
> > > DefaultPlexusContainer.jav
> > > a:436)
> > > at org.apache.maven.execution.MavenSession.lookup
> (MavenSession.java:120)
> > > at
> > >
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.findMappingsForLifecycle
> > > (DefaultLifecycleExecutor.java :938)
> > > ... 17 more
> > > [INFO]
>
> > >
> > ----------------------------------------------------------------------------
> > > [INFO] Total time: 2 seconds
> > > [INFO] Finished at: Wed Sep 28 00:05:24 BST 2005
> > > [INFO] Final Memory: 2M/8M
>
> > > [INFO] ---------------------------------------------------------------
> > >
> > > I read MNG-699, downloaded JarMojo.java-patch.zip and
> > > maven2-ejb3-support.zip successfully compiled and installed these
>
> > pluggins
> > > into a local repository but if I try to build my own simple multi-module
> > > project or the one included in http://www.bzdyl.net/demo-app.zip
> (thks
> > to
> > > Piotrek Bzdyl and all you folks working on m2) I get a lifecycle error !
> > Pls
> > > help :-) thks
> > >
> >
> >
>
>
> --
> .::You're welcome
>
>
