You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/09/23 07:22:22 UTC
[jira] Updated: (MNG-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version
[ 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