You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/25 14:43:35 UTC
[jira] Commented: (MPARTIFACT-19) determine automatically if artifact is a snapshot or not
The following comment has been added to this issue:
Author: Brett Porter
Created: Fri, 25 Jun 2004 8:41 AM
Body:
I'm not sure about this - the whole point is so that we don't need to parse the filename :)
current practice is to set currentVersion to 1.2.0-SNAPSHOT during development - should this be deployed as a timestamped version, or not?
This needs more thought.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPARTIFACT-19?page=comments#action_21016
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT-19
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPARTIFACT-19
Summary: determine automatically if artifact is a snapshot or not
Type: Improvement
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-artifact-plugin
Versions:
1.0
Assignee:
Reporter: Matthias Kerkhoff
Created: Fri, 25 Jun 2004 3:58 AM
Updated: Fri, 25 Jun 2004 8:41 AM
Environment: maven 1.0rc3
Description:
Currently, the artifact plugin defines a taglibary with
tags to install/deploy "release" artifacts and other tags to install/deploy snapshot artifacts.
This distinction, although comprehensible from a technical point of view, should be hidden away from the clients of the artifact plugin.
>From the users point of view there is just an artifact which should be installed or deployed, be it a snapshot or not.
To differ between them introduces unnecessary complexity and also adds possibilities for usage errors (ie, trying to install snapshots, to install-snapshot release versions and so on).
IMHO, there should be only two tags, one to deploy and one to install an artifact. A possible implementation just needs to check the filename for SNAPSHOT_SIGNIFIER. If it is part of the artifacts file name, treat it as a snapshot, otherwise not.
To avoid breaking anything, the proposed tags can be added in addition to the existing tags. After a transition period the current tags should be removed.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report 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