I'm just getting started with Ivy, but one thing that is very
important for me is to easily download source JARs where available.
This runs and places my expected de
Thanks Gabor.
So essentially you're saying that depending on the location of the
build file relative to the location of the lib directory (say 2
directories up the tree), I could in theory put '../..' for the build
location and Ant's smart enough to resolve that on whatever system
it's on? That's
As far as slashes go (and colon or semicolon for classpaths), use the
path syntax that you are comfortable with. Ant will do the platform
specific translation for you. But I'd stick with relative paths, as
Ant will not translate something like C: from Windows into / on UNIX.
Cheers,
Gabor
On Tu
On Tue 2008-06-03 at 12:10h, Shawn Castrianni wrote on ivy-user:
> The ivy.xml contains metadata about an ivy module like name,
> organization, branch, publications, and dependencies. The branch is
> nice to record so we know what branch of source code was used to
> build a given module. However,
Also, terribly sorry for this incredibly n00b question, but I'm
wondering what you would set the ubiquitous ${basedir} property to,
since you want it to be cross platform. Would that be some sort of
relative path? In my build script currently I have basedir (in the
project tag) set to '.'. This
The ivy.xml contains metadata about an ivy module like name, organization,
branch, publications, and dependencies. The branch is nice to record so we
know what branch of source code was used to build a given module. However,
what if the module was built from a tag. Shouldn't we have tag as an
Thanks David.
Clearly my misunderstanding was in the use of the classpath tag. I
tried to use that but was unable to get it work. I'll try sometime
soon.
Do I understand that you're not a fan of dependency management from
the likes of Ivy or Maven then? Gilles recommended that I look into
Ivy
We use a similar strategy more like what DD is describing. At the top
of our "Master Build Script" which everyone's script imports, we have
these tasks (some are from ant contrib) declared outside of a target (so
they always run):
http://an.internal.web.server/master.build.xml";
dest="${u
You should look at http://ant.apache.org/ivy/
2008/6/2 Tim Visher <[EMAIL PROTECTED]>:
> Hello Everyone,
>
> I've been working on setting up an automated build environment using
> Ant for a few days while I try to move towards the Continuous
> Integration benchmark and I've run into a major snag
