You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "David Jackman (JIRA)" <ji...@codehaus.org> on 2005/09/19 17:54:10 UTC

[jira] Created: (MNG-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
----------------------------------------------------------------------------------------------

         Key: MNG-922
         URL: http://jira.codehaus.org/browse/MNG-922
     Project: Maven 2
        Type: New Feature
    Versions: 2.0-beta-1    
 Reporter: David Jackman


This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base.

When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time.  This causes a LOT of artifacts being created when using a continuous build.  Would like to see this "feature" configurable, so I can turn it off at the very least or have it happen only when I want to or on a scheduled basis.

On a related note, I think it would be good for the date/timestamped version to still contain the word SNAPSHOT.  This way, it's very easy to determine whether a project currently has dependencies on snapshot (unreleased) versions.  I can parse for the date/time format as well, but the common SNAPSHOT keyword would be easier.

-- 
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] Closed: (MNG-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

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

    Resolution: Fixed

> Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
> ----------------------------------------------------------------------------------------------
>
>          Key: MNG-922
>          URL: http://jira.codehaus.org/browse/MNG-922
>      Project: Maven 2
>         Type: New Feature
>   Components: maven-artifact
>     Versions: 2.0-beta-1
>     Reporter: David Jackman
>     Assignee: Brett Porter
>      Fix For: 2.0-beta-3

>
> Original Estimate: 1 hour, 30 minutes
>        Time Spent: 45 minutes
>         Remaining: 0 minutes
>
> This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base.
> When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time.  This causes a LOT of artifacts being created when using a continuous build.  Would like to see this "feature" configurable, so I can turn it off at the very least or have it happen only when I want to or on a scheduled basis.
> On a related note, I think it would be good for the date/timestamped version to still contain the word SNAPSHOT.  This way, it's very easy to determine whether a project currently has dependencies on snapshot (unreleased) versions.  I can parse for the date/time format as well, but the common SNAPSHOT keyword would be easier.

-- 
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-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

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

Brett Porter commented on MNG-922:
----------------------------------

<uniqueVersion> is a better name for the tag.

> Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
> ----------------------------------------------------------------------------------------------
>
>          Key: MNG-922
>          URL: http://jira.codehaus.org/browse/MNG-922
>      Project: Maven 2
>         Type: New Feature
>   Components: maven-artifact
>     Versions: 2.0-beta-1
>     Reporter: David Jackman
>     Assignee: Brett Porter
>      Fix For: 2.0-beta-3

>
> Original Estimate: 1 hour, 30 minutes
>         Remaining: 1 hour, 30 minutes
>
> This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base.
> When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time.  This causes a LOT of artifacts being created when using a continuous build.  Would like to see this "feature" configurable, so I can turn it off at the very least or have it happen only when I want to or on a scheduled basis.
> On a related note, I think it would be good for the date/timestamped version to still contain the word SNAPSHOT.  This way, it's very easy to determine whether a project currently has dependencies on snapshot (unreleased) versions.  I can parse for the date/time format as well, but the common SNAPSHOT keyword would be easier.

-- 
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-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

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

Brett Porter updated MNG-922:
-----------------------------

    Fix Version: 2.0-beta-3

> Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
> ----------------------------------------------------------------------------------------------
>
>          Key: MNG-922
>          URL: http://jira.codehaus.org/browse/MNG-922
>      Project: Maven 2
>         Type: New Feature
>   Components: maven-artifact
>     Versions: 2.0-beta-1
>     Reporter: David Jackman
>      Fix For: 2.0-beta-3

>
>
> This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base.
> When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time.  This causes a LOT of artifacts being created when using a continuous build.  Would like to see this "feature" configurable, so I can turn it off at the very least or have it happen only when I want to or on a scheduled basis.
> On a related note, I think it would be good for the date/timestamped version to still contain the word SNAPSHOT.  This way, it's very easy to determine whether a project currently has dependencies on snapshot (unreleased) versions.  I can parse for the date/time format as well, but the common SNAPSHOT keyword would be easier.

-- 
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-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

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

Brett Porter updated MNG-922:
-----------------------------

    Remaining Estimate: 1 hour, 30 minutes
     Original Estimate: 5400

> Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
> ----------------------------------------------------------------------------------------------
>
>          Key: MNG-922
>          URL: http://jira.codehaus.org/browse/MNG-922
>      Project: Maven 2
>         Type: New Feature
>   Components: maven-artifact
>     Versions: 2.0-beta-1
>     Reporter: David Jackman
>      Fix For: 2.0-beta-3

>
> Original Estimate: 1 hour, 30 minutes
>         Remaining: 1 hour, 30 minutes
>
> This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base.
> When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time.  This causes a LOT of artifacts being created when using a continuous build.  Would like to see this "feature" configurable, so I can turn it off at the very least or have it happen only when I want to or on a scheduled basis.
> On a related note, I think it would be good for the date/timestamped version to still contain the word SNAPSHOT.  This way, it's very easy to determine whether a project currently has dependencies on snapshot (unreleased) versions.  I can parse for the date/time format as well, but the common SNAPSHOT keyword would be easier.

-- 
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-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

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

Brett Porter commented on MNG-922:
----------------------------------

ok, so in <snapshotRepository> in <distributionManagement>, will add an option <trackBuild> which defaults to "true". If false, then SNAPSHOT will be used instead. This should just involve not writing the build & timestamp to the metadata on deployment.

> Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
> ----------------------------------------------------------------------------------------------
>
>          Key: MNG-922
>          URL: http://jira.codehaus.org/browse/MNG-922
>      Project: Maven 2
>         Type: New Feature
>   Components: maven-artifact
>     Versions: 2.0-beta-1
>     Reporter: David Jackman
>     Assignee: Brett Porter
>      Fix For: 2.0-beta-3

>
> Original Estimate: 1 hour, 30 minutes
>         Remaining: 1 hour, 30 minutes
>
> This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base.
> When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time.  This causes a LOT of artifacts being created when using a continuous build.  Would like to see this "feature" configurable, so I can turn it off at the very least or have it happen only when I want to or on a scheduled basis.
> On a related note, I think it would be good for the date/timestamped version to still contain the word SNAPSHOT.  This way, it's very easy to determine whether a project currently has dependencies on snapshot (unreleased) versions.  I can parse for the date/time format as well, but the common SNAPSHOT keyword would be easier.

-- 
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-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

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

Brett Porter updated MNG-922:
-----------------------------

    Component: maven-artifact

> Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
> ----------------------------------------------------------------------------------------------
>
>          Key: MNG-922
>          URL: http://jira.codehaus.org/browse/MNG-922
>      Project: Maven 2
>         Type: New Feature
>   Components: maven-artifact
>     Versions: 2.0-beta-1
>     Reporter: David Jackman

>
>
> This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base.
> When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time.  This causes a LOT of artifacts being created when using a continuous build.  Would like to see this "feature" configurable, so I can turn it off at the very least or have it happen only when I want to or on a scheduled basis.
> On a related note, I think it would be good for the date/timestamped version to still contain the word SNAPSHOT.  This way, it's very easy to determine whether a project currently has dependencies on snapshot (unreleased) versions.  I can parse for the date/time format as well, but the common SNAPSHOT keyword would be easier.

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