Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v753)
To: ivy-user@ant.apache.org
Message-Id: <18B1BCC2-33BA-4639-BF38-7F35ECE083D9@dockter.biz>
Content-Type: multipart/alternative; boundary=Apple-Mail-2--522573526
From: Hans Dockter <mail@dockter.biz>
Subject: Publishing ivy files
Date: Wed, 23 Jan 2008 22:15:25 +0100

--Apple-Mail-2--522573526
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

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


--Apple-Mail-2--522573526--