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 2008/07/06 18:14:26 UTC

[jira] Created: (MNG-3656) Collect all version information in the top-level POM, and manage with a set of properties

Collect all version information in the top-level POM, and manage with a set of properties
-----------------------------------------------------------------------------------------

                 Key: MNG-3656
                 URL: http://jira.codehaus.org/browse/MNG-3656
             Project: Maven 2
          Issue Type: Bug
    Affects Versions: 2.0-alpha-1
            Reporter: Jason van Zyl


The impetus is to control the versions used from one simple location. We have had many proposals in the past, but in the short term a set of properties is easy to manipulate using execution request properties. This allows the collection in small, short span in the POM and will allow the easy swapping of versions for inter-component/library integration builds.

-- 
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-3656) Collect all version information in the top-level POM, and manage with a set of properties

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

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

This is really a best practice at this point. Not a bug.

> Collect all version information in the top-level POM, and manage with a set of properties
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-3656
>                 URL: http://jira.codehaus.org/browse/MNG-3656
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 2.0-alpha-1, 3.0-alpha-1
>            Reporter: Jason van Zyl
>
> The impetus is to control the versions used from one simple location. We have had many proposals in the past, but in the short term a set of properties is easy to manipulate using execution request properties. This allows the collection in small, short span in the POM and will allow the easy swapping of versions for inter-component/library integration builds.

-- 
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-3656) Collect all version information in the top-level POM, and manage with a set of properties

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

Brett Porter updated MNG-3656:
------------------------------

    Affects Version/s: 2.1-alpha-1
        Fix Version/s: 2.1-alpha-2

was this already done?

> Collect all version information in the top-level POM, and manage with a set of properties
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-3656
>                 URL: http://jira.codehaus.org/browse/MNG-3656
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0-alpha-1, 2.1-alpha-1
>            Reporter: Jason van Zyl
>             Fix For: 2.1-alpha-2
>
>
> The impetus is to control the versions used from one simple location. We have had many proposals in the past, but in the short term a set of properties is easy to manipulate using execution request properties. This allows the collection in small, short span in the POM and will allow the easy swapping of versions for inter-component/library integration builds.

-- 
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-3656) Collect all version information in the top-level POM, and manage with a set of properties

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

Jason van Zyl closed MNG-3656.
------------------------------

       Resolution: Incomplete
    Fix Version/s:     (was: 3.x)

> Collect all version information in the top-level POM, and manage with a set of properties
> -----------------------------------------------------------------------------------------
>
>                 Key: MNG-3656
>                 URL: http://jira.codehaus.org/browse/MNG-3656
>             Project: Maven 2 & 3
>          Issue Type: Bug
>    Affects Versions: 2.0-alpha-1, 3.0-alpha-1
>            Reporter: Jason van Zyl
>
> The impetus is to control the versions used from one simple location. We have had many proposals in the past, but in the short term a set of properties is easy to manipulate using execution request properties. This allows the collection in small, short span in the POM and will allow the easy swapping of versions for inter-component/library integration builds.

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