[ http://jira.codehaus.org/browse/MPARTIFACT-19?page=all ]
Brett Porter closed MPARTIFACT-19:
----------------------------------
Resolution: Fixed
> determine automatically if artifact is a snapshot or not
> --------------------------------------------------------
>
> Key: MPARTIFACT-19
> URL: http://jira.codehaus.org/browse/MPARTIFACT-19
> Project: maven-artifact-plugin
> Type: Improvement
> Versions: 1.0
> Environment: maven 1.0rc3
> Reporter: Matthias Kerkhoff
> Priority: Minor
> Fix For: 1.5
>
>
> 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.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
