[
http://jira.codehaus.org/browse/MANTTASKS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann moved MNG-2273 to MANTTASKS-137:
--------------------------------------------------
Affects Version/s: (was: 2.0.4)
2.0.4
Component/s: (was: Ant tasks)
dependencies task
Key: MANTTASKS-137 (was: MNG-2273)
Project: Maven 2.x Ant Tasks (was: Maven 2)
> <dependencies> task gives a bad pathId when downloading a deployed SNAPSHOT
> ---------------------------------------------------------------------------
>
> Key: MANTTASKS-137
> URL: http://jira.codehaus.org/browse/MANTTASKS-137
> Project: Maven 2.x Ant Tasks
> Issue Type: Bug
> Components: dependencies task
> Affects Versions: 2.0.4
> Reporter: Dan Fabulich
> Assignee: Brett Porter
> Priority: Blocker
>
> Deploy a -SNAPSHOT build using the deploy:deploy-file goal. (Don't do it
> with the <deploy> Ant task; that doesn't work, per bug MNG-2060.) The file
> will be deployed into a -SNAPSHOT directory, but the file itself will contain
> a build number, not the word SNAPSHOT.
> Now delete the SNAPSHOT from your local repository and attempt to use
> <dependencies> to acquire it. The task will claim to succeed, but the pathId
> will contain an incorrect file path.
> For example, I deployed selenium-server-0.7.2-SNAPSHOT.jar; on the remote
> repo it was called selenium-server-0.7.2-20060505.015135-1.jar. When the Ant
> task pulled it into my local repo it was in
> selenium-server\0.7.2-SNAPSHOT\selenium-server-0.7.2-20060505.015135-1.jar.
> But finally when I ran the Ant task, the classpath it gave me pointed to
> selenium-server\0.7.2-20060505.015135-1\selenium-server-0.7.2-20060505.015135-1.jar,
> which is clearly wrong.
--
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
