You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/12/13 19:53:19 UTC
[jira] Moved: (MANTTASKS-136) Deploy Ant task doesn't handle
-SNAPSHOT
[ http://jira.codehaus.org/browse/MANTTASKS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-2269 to MANTTASKS-136:
--------------------------------------------------
Component/s: (was: Ant tasks)
deploy task
Key: MANTTASKS-136 (was: MNG-2269)
Project: Maven 2.x Ant Tasks (was: Maven 2)
> Deploy Ant task doesn't handle -SNAPSHOT
> ----------------------------------------
>
> Key: MANTTASKS-136
> URL: http://jira.codehaus.org/browse/MANTTASKS-136
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: deploy task
> Reporter: Dan Fabulich
> Assignee: Carlos Sanchez
>
> Use the Maven "deploy" ant task with the version "1.0-SNAPSHOT". It will be deployed to the artifact repository as "1.0-SNAPSHOT"; it won't have its -SNAPSHOT replaced with a proper qualified name (timestamp, build number, etc.).
> Ideally there would be a way for users to specify their own qualifier in the Ant task, by specifying a special attribute. That would allow Ant scripters to use Ant's <BuildNumber> task or to use any other arbitrary build number as needed.
--
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