[
https://jira.codehaus.org/browse/MPLUGIN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300156#comment-300156
]
Brett Porter commented on MPLUGIN-109:
--------------------------------------
This is no longer the case - you can configure
{{<skipErrorNoDescriptorsFound>true</skipErrorNoDescriptorsFound>}} to avoid
the error. This is preferable to using the {{jar}} packaging type, as when that
is used as a plugin it warns about a missing plugin descriptor on every build.
> Misleading warning when creating a Maven plugin defining a custom packaging
> ---------------------------------------------------------------------------
>
> Key: MPLUGIN-109
> URL: https://jira.codehaus.org/browse/MPLUGIN-109
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 2.4.1
> Reporter: Ludovic Claude
> Assignee: John Casey
> Priority: Minor
> Fix For: 2.5
>
> Attachments: console.log, test-custom-packaging.zip
>
>
> When creating a custom packaging using the 2.4.1 version of the
> maven-plugin-plugin, I'm getting the following warning message:
> [INFO] Building foobar-maven-plugin
> [INFO] task-segment: [install]
> [INFO]
> ------------------------------------------------------------------------
> [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.
> [WARNING]
> [WARNING]
> [WARNING] *******************************************************
> [WARNING] Deprecation Alert:
> [WARNING] No mojo descriptors were found in this project which has a
> packaging type of maven-plugin.
> [WARNING] In future versions of the plugin tools, this will fail the build.
> [WARNING] If this project is an archetype, change the packaging type from
> maven-plugin to maven-archetype.
> [WARNING] ********************************************************
> Indeed, my project contains no Mojos, only a plexus components.xml file. Now
> if you try to enforce a rule that says that a maven-plugin must contain at
> least one Mojo (see MPLUGIN-106), that's fine, but which packaging am I
> supposed to use to create a plugin that defines a new packaging (here, the
> foobar packaging)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
