test
Consorsbank und DAB BNP Paribas sind eingetragene Marken der BNP Paribas S.A.
Niederlassung Deutschland (AG nach franz. Recht).
Sitz der BNP Paribas S.A. Niederlassung Deutschland: Bahnhofstraße 55, 90402
Nürnberg, HRB Nürnberg 31129, USt-IdNr. DE191528929
Fon +49 (0) 911 / 369-0, Fax +49
Hi Everyone,
I'm new to Ivy and I have a question regarding dependencies associated with
the test configuration. I have 2 modules, Module A and Module B. I have
non-standard configurations java-test and java. Java test gets mapped
to the test configuration in Ivy. I have dependencies listed
Vonnahme, Paul wrote on 05/19/2009 01:26 PM:
I'm hoping someone else is in a similar situation. We have some
utility jars used by multiple projects. These jars have three
different versions: one each for our test, pilot, and production
environments. Therefore I believe each
can use Ant properties (not variables) in
ivysettings.xml files, *not *ivy.xml files as you say.
and run in test environment:
ant -Divy.build.env=integration compile
You can even default the property in ivysettings.xml, with an
override=false setting, to ensure your command-line
I'm hoping someone else is in a similar situation. We have some utility jars
used by multiple projects. These jars have three different versions: one each
for our test, pilot, and production environments. Therefore I believe each of
the versions needs to be published so it will be available
Vonnahme, Paul wrote on 05/19/2009 01:26 PM:
I'm hoping someone else is in a similar situation. We have some
utility jars used by multiple projects. These jars have three
different versions: one each for our test, pilot, and production
environments. Therefore I believe each of the versions needs
environment. If your situation is more complicated
and you need to fetch different versions of an upstream JAR into the same
downstream project for different purposes (unit test, deployment, etc.),
look into Ivy configurations. They're designed to do exactly what you
want.
In our project we have
is more complicated
and you need to fetch different versions of an upstream JAR into the same
downstream project for different purposes (unit test, deployment, etc.),
look into Ivy configurations. They're designed to do exactly what you want.
In our project we have a unit testing version of some
When I checked out the trunk earlier today there was only one test failure. It
was IBiblioResolverTest.testMaven2Listing that failed. The resolution of
commons-lang was returning two module entries rather than the expected one. The
expected module entry was named commons-lang but an additional
Sent: Monday, October 27, 2008 5:49:40 PM
Subject: Test failures in SVN
Speaking of iBiblio, some related tests are failing for me with the
current SVN head:
http://pastebin.com/m63ca1e7
Jim
Speaking of iBiblio, some related tests are failing for me with the
current SVN head:
http://pastebin.com/m63ca1e7
Jim
11 matches
Mail list logo
