[ 
https://issues.apache.org/jira/browse/IVY-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832511#comment-13832511
 ] 

Nicolas Lalevée commented on IVY-1431:
--------------------------------------

The patch looks really great. I see the doc has been updated which is really 
nice.
I would just need some little time to test it a little bit.

There maybe just a little hitch. In the test file 
{{test/repositories/ivysettings.xml}} I see an url concatenation: 
file:${ivy.settings.dir}/m2. From experience, this doesn't work on Windows, and 
there is no proper way make an url concatenation work on every platform. But I 
could be wrong. And it's not a blocker for me for the patch to be integrated.

> Also copy original metadata artifact (e.g. POM) on ivy:install
> --------------------------------------------------------------
>
>                 Key: IVY-1431
>                 URL: https://issues.apache.org/jira/browse/IVY-1431
>             Project: Ivy
>          Issue Type: Improvement
>            Reporter: Erwin Tratar
>            Priority: Minor
>              Labels: patch
>         Attachments: ivy-1431.patch, ivy-install-pom.patch
>
>
> Suppose you provide some module, which you are developing with Ivy and that 
> has external dependencies (or even worse: non publically available 
> dependencies). Then you might want to publish the module plus all 
> dependencies to a filesystem repository, which then can be redistributed and 
> which is usable for offline builds. 
> So far, no problem. But if you do not want to or even can't force your 
> consumers to use Ivy, then while you can create this "offline repository" in 
> Maven layout, it still is not usable with Maven because the POMs of all your 
> dependencies are missing. While Ivy remembers them (*.orig Files), they are 
> not used.
> The attached patch will copy the cached original metadata in the install 
> operation if it's type ends in ".original". Also, the restoring of the 
> OriginArtifact from the Cache is modified to actually restore the 
> OriginArtifact's orignal Artifact correctly.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to