I avoid using latest.integration because it always has to go back to the
repo to check for a later version rather than use the cache.
It does mean you have to release a new version of your 3rd tier
dependencies to get a change in your first tier picked up but I see that
as a good thing.
R
On 21/03/12 07:03, 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.
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.
