[
https://issues.apache.org/jira/browse/IVY-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580307#action_12580307
]
Damien B commented on IVY-651:
------------------------------
"Or maybe we can just give an the instruction of where the files should be
copied (resolving the artifact pattern of the shared repository if any),
instead of trying to use Ivy which is almost more difficult for something as
easy as a file copy."
Right now it's not really as easy as a file copy (in a ivy:install scenario),
because putting the jar in the final repository has no effect, even by creating
manually the md5 and sha1 files. What works is to put the manually downloaded
jar, and putting it in the cache repository, which is a little bit
counter-intuitive, given that several people can do an ivy:install on a
repository, which means that the error will be reported over and over everytime
the dependency is involved.
> Ivy should be able to handle downloadUrl in POM
> -----------------------------------------------
>
> Key: IVY-651
> URL: https://issues.apache.org/jira/browse/IVY-651
> Project: Ivy
> Issue Type: Improvement
> Affects Versions: 2.0.0-alpha-2
> Reporter: Nat
> Fix For: 2.0
>
>
> In Maven2, sometimes there is no jar files in the specified location but the
> downloadUrl is specified in POM. Ivy should be able to redirect to download
> the correct jar files from the specified location.
> For example,
> http://repo1.maven.org/maven2/com/bea/wlplatform/commonj-twm/1.1/commonj-twm-1.1.pom
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
