You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Nils Fredrik Gjerull (JIRA)" <ji...@codehaus.org> on 2006/01/03 20:27:12 UTC

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

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: http://jira.codehaus.org/browse/MNG-1915
     Project: Maven 2
        Type: Bug

  Components: Reactor and workspace  
    Versions: 2.0.1    
    Reporter: Nils Fredrik Gjerull


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 contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1915?page=all ]

Brett Porter updated MNG-1915:
------------------------------

    Fix Version: 2.1

but do you want to create something at the top level that contains all of those and rebundles them? This is usually how the assembly plugin works, for example.

I think we need to support this, but after more careful consideration of how the module relationship equates to the dependency relationship usually used to build these.

> 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: http://jira.codehaus.org/browse/MNG-1915
>      Project: Maven 2
>         Type: Bug

>   Components: Reactor and workspace
>     Versions: 2.0.1
>     Reporter: Nils Fredrik Gjerull
>      Fix For: 2.1

>
>
> 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 contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1915?page=comments#action_54944 ] 

Brett Porter commented on MNG-1915:
-----------------------------------

so, this is an aggregating artifact?

> 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: http://jira.codehaus.org/browse/MNG-1915
>      Project: Maven 2
>         Type: Bug

>   Components: Reactor and workspace
>     Versions: 2.0.1
>     Reporter: Nils Fredrik Gjerull

>
>
> 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 contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

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

Posted by "Nils Fredrik Gjerull (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1915?page=comments#action_54989 ] 

Nils Fredrik Gjerull commented on MNG-1915:
-------------------------------------------

I am not sure what you mean by aggregating artifact. What I want to do is to run all the sub projects until the package phase. After that I want to move the packaged sub projects (the boot module and the jpf plug-ins) into the target directory of the master project. So if you run the install phase of the master project you are able to start the jpf application from the target directory.

> 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: http://jira.codehaus.org/browse/MNG-1915
>      Project: Maven 2
>         Type: Bug

>   Components: Reactor and workspace
>     Versions: 2.0.1
>     Reporter: Nils Fredrik Gjerull

>
>
> 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 contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

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

Posted by "Nils Fredrik Gjerull (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1915?page=comments#action_54880 ] 

Nils Fredrik Gjerull commented on MNG-1915:
-------------------------------------------

I am working on creating a maven2 plug-in for Java Plug-in Framework ([http://jpf.sourceforge.net/]). This framework is inspired by Eclipse. I would like to be able to use maven2 to build applications using this framework. To do this I would like to have a master project (quite like the "pom" packaging, but with different implementations of the validate, install and deploy phases). The modules in the master project would bee the boot module and all  the plug-ins needed for a functioning system.

> 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: http://jira.codehaus.org/browse/MNG-1915
>      Project: Maven 2
>         Type: Bug

>   Components: Reactor and workspace
>     Versions: 2.0.1
>     Reporter: Nils Fredrik Gjerull

>
>
> 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 contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org

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

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1915?page=comments#action_54820 ] 

Brett Porter commented on MNG-1915:
-----------------------------------

This was already closed WON'T FIX in MNG-1760.

Do you have a specific use case for the inclusion of this?

> 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: http://jira.codehaus.org/browse/MNG-1915
>      Project: Maven 2
>         Type: Bug

>   Components: Reactor and workspace
>     Versions: 2.0.1
>     Reporter: Nils Fredrik Gjerull

>
>
> 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 contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org