You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2014/01/19 22:51:49 UTC

[jira] (MNG-1915) Top level project have to have a packaging of "pom". What about plug-ins wanting to make a different top level packaging?

    [ https://jira.codehaus.org/browse/MNG-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338850#comment-338850 ] 

Jason van Zyl commented on MNG-1915:
------------------------------------

You can create your own lifecycle and package it up in an extension and use it, works inside m2e as well.
                
> Top level project have to have a packaging of "pom". What about plug-ins wanting to make a different top level packaging?
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-1915
>                 URL: https://jira.codehaus.org/browse/MNG-1915
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Reactor and workspace
>    Affects Versions: 2.0.1
>            Reporter: Nils Fredrik Gjerull
>             Fix For: Issues to be reviewed for 3.x
>
>
> The issue number MNG-764 included a patch that made maven check if the pom containing {{<module>}} elements had a packaging of pom. What if a plug-in want to create a different top level packaging?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira