[ https://issues.apache.org/jira/browse/COCOON-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738946#action_12738946 ]
Andreas Hartmann edited comment on COCOON-2240 at 8/4/09 5:31 AM: ------------------------------------------------------------------ Thorsten's solution didn't work for me, but this did (in the parent POM pluginManagement section): <plugin> <groupId>org.apache.cocoon</groupId> <artifactId>cocoon-maven-plugin</artifactId> <version>1.0.0-M2</version> <executions> <execution> <id>prepare</id> <phase>compile</phase> <goals> <goal>prepare</goal> </goals> </execution> </executions> <dependencies> <dependency> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.1-beta-1</version> </dependency> </dependencies> </plugin> was (Author: andr...@apache.org): Thorstens solution didn't work for me, but this did (in the parent POM pluginManagement section): <plugin> <groupId>org.apache.cocoon</groupId> <artifactId>cocoon-maven-plugin</artifactId> <version>1.0.0-M2</version> <executions> <execution> <id>prepare</id> <phase>compile</phase> <goals> <goal>prepare</goal> </goals> </execution> </executions> <dependencies> <dependency> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.1-beta-1</version> </dependency> </dependencies> </plugin> > Building all blocks from parent pom doesn't work > ------------------------------------------------ > > Key: COCOON-2240 > URL: https://issues.apache.org/jira/browse/COCOON-2240 > Project: Cocoon > Issue Type: Bug > Components: - Build System: Maven > Affects Versions: 2.2 > Reporter: Stephan > > This seems to be similar to https://issues.apache.org/jira/browse/COCOON-2007. > I created two cocoon blocks and a webapp like this: > webapp > block1 > block2 > Then, I created a parent pom that referes to these modules in order to be > able to build all at once. But when I execute "mvn install" within my parent > project, I got this error: > org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the > plugin manager executing goal 'org.apache.maven.plugins:maven-war-plugin > :2.0.2:war': Unable to find the mojo > 'org.apache.maven.plugins:maven-war-plugin:2.0.2:war' in the plugin > 'org.apache.maven.plugins:maven-war-plugin' > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:562) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > 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.apache.maven.plugin.PluginManagerException: Unable to find the > mojo 'org.apache.maven.plugins:maven-war-plugin:2.0.2:war' in the plugin > 'org.apache.maven.plugins:maven-war-plugin' > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:618) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:429) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > ... 16 more > Caused by: > org.codehaus.plexus.component.repository.exception.ComponentLookupException: > Component descriptor cannot be found in the component reposito > ry: > org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-war-plugin:2.0.2:war. > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:312) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:609) > ... 18 more > Deleting the whole maven repo and downloading all plugins and dependencies > again didn't work. > Changing the version of the mvn-war-plugin to 2.1-alpha-1 as suggested here > (http://www.nabble.com/Creating-a-parent-POM-td18173518.html) worked, but is > it right to depend on a alpha version? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.