You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stefan Franke (JIRA)" <ji...@codehaus.org> on 2008/12/08 15:18:19 UTC

[jira] Created: (MNG-3894) provide an include mechanism to include other pom.xml

provide an include mechanism to include other pom.xml
-----------------------------------------------------

                 Key: MNG-3894
                 URL: http://jira.codehaus.org/browse/MNG-3894
             Project: Maven 2
          Issue Type: Improvement
          Components: Inheritance and Interpolation
         Environment: any
            Reporter: Stefan Franke


The idea to manage project independent templates is not new. But it is not possible to do this with maven and neither inheritance nor the dependency mechanism is enough.

The include mechnism would include the requested pom (including ist parent poms) as if the containing elements where part of the current pom. Thus allowing to use every available pom mechanism. On conflict local pom settings wins.

Very useful and needed to reduce redundancy between different projects!

-- 
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

        

[jira] Updated: (MNG-3894) provide an include mechanism to include other pom.xml

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-3894:
------------------------------

    Fix Version/s: 3.x

mixins are being considered for Maven 3.0

> provide an include mechanism to include other pom.xml
> -----------------------------------------------------
>
>                 Key: MNG-3894
>                 URL: http://jira.codehaus.org/browse/MNG-3894
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>         Environment: any
>            Reporter: Stefan Franke
>             Fix For: 3.x
>
>
> The idea to manage project independent templates is not new. But it is not possible to do this with maven and neither inheritance nor the dependency mechanism is enough.
> The include mechnism would include the requested pom (including ist parent poms) as if the containing elements where part of the current pom. Thus allowing to use every available pom mechanism. On conflict local pom settings wins.
> Very useful and needed to reduce redundancy between different projects!

-- 
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

        

[jira] Commented: (MNG-3894) provide an include mechanism to include other pom.xml

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204359#action_204359 ] 

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

You can use scope = import today for many cases.

> provide an include mechanism to include other pom.xml
> -----------------------------------------------------
>
>                 Key: MNG-3894
>                 URL: http://jira.codehaus.org/browse/MNG-3894
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>         Environment: any
>            Reporter: Stefan Franke
>
> The idea to manage project independent templates is not new. But it is not possible to do this with maven and neither inheritance nor the dependency mechanism is enough.
> The include mechnism would include the requested pom (including ist parent poms) as if the containing elements where part of the current pom. Thus allowing to use every available pom mechanism. On conflict local pom settings wins.
> Very useful and needed to reduce redundancy between different projects!

-- 
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

        

[jira] Closed: (MNG-3894) provide an include mechanism to include other pom.xml

Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl closed MNG-3894.
------------------------------

       Resolution: Not A Bug
    Fix Version/s:     (was: 3.x)

> provide an include mechanism to include other pom.xml
> -----------------------------------------------------
>
>                 Key: MNG-3894
>                 URL: http://jira.codehaus.org/browse/MNG-3894
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Inheritance and Interpolation
>         Environment: any
>            Reporter: Stefan Franke
>
> The idea to manage project independent templates is not new. But it is not possible to do this with maven and neither inheritance nor the dependency mechanism is enough.
> The include mechnism would include the requested pom (including ist parent poms) as if the containing elements where part of the current pom. Thus allowing to use every available pom mechanism. On conflict local pom settings wins.
> Very useful and needed to reduce redundancy between different projects!

-- 
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