Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com
 designates 209.85.198.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=RlddhDH5sBfQsmLd6CSmQJQMPV3OdtS4ZEu/3wLhhtepOwYmc07hKKbGTYzTMK2xLWHtrOxOBoMbEhGocSO5uw3Pl2NKBeGIBgvFBHCB9wUXRS/9MMSIbpMiRzCFo19qzlfy17tC+jX0c7SudcjIpJ+mOQAPSmwKTzXn80tbiK0=
Message-ID: <635a05060801280020q3d4d980dv1fce75542314bc17@mail.gmail.com>
Date: Mon, 28 Jan 2008 09:20:29 +0100
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@ant.apache.org
Subject: Re: Publishing ivy files
In-Reply-To: <A2C712A8-CB6F-4277-BE3B-1A834AECBE0B@dockter.biz>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_2953_31176385.1201508429539"
References: <18B1BCC2-33BA-4639-BF38-7F35ECE083D9@dockter.biz>
	 <A2C712A8-CB6F-4277-BE3B-1A834AECBE0B@dockter.biz>

------=_Part_2953_31176385.1201508429539
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You need to provide an Ivy file for Ivy to publish it. But generating the
file on the fly is very easy with the module descriptor, you just have to
use XmlModuleDescriptorWriter.

Xavier

On Jan 23, 2008 10:20 PM, Hans Dockter <mail@dockter.biz> wrote:

> I would like to add that so far I use for publishing the following
> method of the PublishEngine:
>
> public Collection publish(ModuleDescriptor md, Collection
> srcArtifactPattern,
>             DependencyResolver resolver, PublishOptions options)
> throws IOException { ...
>
> - Hans
>
> On Jan 23, 2008, at 10:15 PM, Hans Dockter wrote:
>
> > I have the following requirement. My build tool, which uses ivy
> > under the hood, does not work with ivy files. It uses Ivy via its
> > API and thus creates the ModuleDescriptors, DependencyDescriptors,
> > etc ... My problem is to publish a module via its
> > ModuleDescriptors. The artifacts are published without any
> > problems. But I want the ivy file also to be published to the
> > repository. But locally there exists no ivy file. Only the
> > ModuleDescriptor exists in memory.
> >
> > Is there a way that Ivy does the ivy file generation on the fly for
> > publishing? Or do I have to locally generate a temporary ivy file,
> > to get it published?
> >
> > - Hans
> >
>
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/

------=_Part_2953_31176385.1201508429539--