Return-Path: X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0147610E03 for ; Tue, 20 Aug 2013 10:45:24 +0000 (UTC) Received: (qmail 49401 invoked by uid 500); 20 Aug 2013 10:45:17 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 49169 invoked by uid 500); 20 Aug 2013 10:45:17 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 48326 invoked by uid 99); 20 Aug 2013 10:45:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Aug 2013 10:45:02 +0000 Date: Tue, 20 Aug 2013 10:45:02 +0000 (UTC) From: "Erwin Tratar (JIRA)" To: notifications@ant.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IVY-1431) Also copy original metadata artifact (e.g. POM) on ivy:install MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IVY-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwin Tratar updated IVY-1431: ------------------------------ Attachment: ivy-install-pom.patch > 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 > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira