Cameron, Just take the ZIPs in MOJO-98 and MOJO-99 and invoke mvn install on them.
Cheers, Stéphane On 11/15/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 > > -- .::You're welcome ::.