[
https://issues.apache.org/jira/browse/IVY-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812677#comment-13812677
]
Erwin Tratar commented on IVY-1431:
-----------------------------------
New metadata is nice, but only relying on the metadata would require everyone
to throw away their caches. So maybe add the metadata and use it, but if it's
not available perform the "reverse engineeing", as it could be cached with a
previous version.
The last 2 checks are there to only install the original metadata if the type
(e.g. "pom.original") is different from the actual metadata (i.e. "ivy" +
".original"). So if the dependency is not from a m2 repo, then no original
metadata is installed.
I will update the patch with additional metadata (with fallback) and
"installOriginalMetadata".
> 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-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)
