Good for you, it also took me the better part of the afternoon to get a
working ivy.xml. I would suggest providing some more tutorials around
the configuration concept.
Just to clarify: right now I'm trying to setup different collections of
jars for building and testing. E.g. I have a set with jars that are
required for building, which differs from the runtime set and from the
test set.
For example:
- runtime = log4j, commons this, commons that, framework here, ...
- build = runtime + servlet.api (servlet api is provided by the
container, so not part of the deliverable/runtime, but required for
compiling the sources)
- test = runtime + junit, hsqldb
In the end it is simple, but never the less... Since this maybe is a
common setup, it might make a good example.
Joshua Tharp wrote:
Nevermind. I think I figured out what I was doing wrong.
On Tue, Apr 21, 2009 at 4:19 PM, Joshua Tharp <
[email protected]> wrote:
Serious ivy newbie alert
I am utterly baffled by the configuration mechanism with Ivy.
