I had the same issue but changing the \org\apache\cocoon\cocoon\6 \cocoon-6.pom
in my local repository resolved the issue. I found that workaround somewhere
online.
<dependency>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-alpha-1</version>
</dependency>
Robby
-----Original Message-----
From: Thorsten Scherler (JIRA) [mailto:j...@apache.org]
Sent: Wednesday, July 22, 2009 2:51 PM
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-2240) Building all blocks from parent pom
doesn't work
[
https://issues.apache.org/jira/browse/COCOON-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734100#action_12734100
]
Thorsten Scherler commented on COCOON-2240:
-------------------------------------------
adding
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-1</version>
</plugin>
</plugins>
</pluginManagement>
In your parent pom as well is working fine.
> 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.
