[
http://jira.codehaus.org/browse/MPLUGIN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128168
]
James Carman commented on MPLUGIN-102:
--------------------------------------
Ok, so the old documentation was wrong? That means that there are probably
lots (as many people who were willing to write their own archetypes for maven
:-) of folks out there using maven-plugin as their packaging in their
archetypes. The unfortunate thing is that this actually worked in the past and
now it doesn't.
> The 2.4 Release Breaks Previously-Working Builds
> ------------------------------------------------
>
> Key: MPLUGIN-102
> URL: http://jira.codehaus.org/browse/MPLUGIN-102
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 2.4
> Environment: Maven version: 2.0.8
> Java version: 1.5.0_14
> OS name: "windows vista" version: "6.0" arch: "x86" Family: "windows"
> Reporter: James Carman
> Attachments: archetype-test.zip, debug.log
>
>
> We have an archetype contained within our project. Today, when I tried to
> run our build, I got the following error:
> [INFO] [plugin:descriptor]
> [INFO] Using 2 extractors.
> [INFO] Applying extractor for language: java
> [INFO] Extractor for language: java found 0 mojo descriptors.
> [INFO] Applying extractor for language: bsh
> [INFO] Extractor for language: bsh found 0 mojo descriptors.
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error extracting plugin descriptor: 'No mojo descriptors found in
> plugin.'
> However, if I add this to my pom.xml file for that module:
> <pluginManagement>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-plugin-plugin</artifactId>
> <version>2.3</version>
> </plugin>
> </plugins>
> </pluginManagement>
> the build works just fine, as usual (understandable since the 2.4 release
> came out yesterday).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
