On 3/20/2012 11:03 AM, David Sills wrote:
I see that the Ivy way is better once you are using Ivy, but it's
frustrating when I can't figure out how to publish sources in the first
place....
-----Original Message-----
From: Not Zippy [mailto:notzi...@gmail.com]
Sent: Tuesday, March 20, 2012 2:01 PM
To: ivy-user@ant.apache.org
Subject: Re: 2 Questions for ivyIDE
Eclipse may be a bit more flexible, but it is better to encapsulate it
the way ivy does.
Well, the way I'd look at it is that Eclipse allows you to define how
things are used in the scope of a project (or workspace) - the classpath
in Eclipse is metadata describing the organization of the project which
you store in the project.
On the other hand, Ivy allows you to generate things which may be used
outside of the specific project in which they were created by using the
publications element to create artifacts such as jars, sources, etc.
Alan
On Tue, Mar 20, 2012 at 10:57 AM, David Sills
<dsi...@datasourceinc.com>wrote:
Oh, Alan, and what I meant is that on the regular Eclipse project
classpath one is allowed to supply source code locations along with a
JAR file added to the classpath. This can be another JAR or a
directory.
I understand now that Ivy processes this differently. Pity, since the
Eclipse methodology is far more flexible.
