I guess the problem scomes from the conf mapping you have in c:
The '%' is used to mean all other configurations, when you start by mapping
other configurations. If you have only one conf mapping, it has no meaning,
you should use '*' instead.
That being said, we can consider this as a bug, sinc
my fault, I introduced a dependency cycle in Gump which should be
fixed now.
sorry for the noise
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi, it looks like the bz2 attachment was removed; I uploaded it to
http://aditsu.net/test.tar.bz2
Also, I just realized this is a general Ant dev list, I should make it clearer
that I'm talking about Ivy.
Adrian
- Original Message
From: Adrian Sandor <[EMAIL PROTECTED]>
To: dev@ant.apa
Hi, I'm using ivy-2.0.0-beta1, and I think I found a bug in the resolver.
I have a custom repository, containing the stuff in the attached test.tar.bz2,
and trying to resolve the attached ivy.xml.
The result is an unresolved dependency: "test#b;1: configuration(s) not found
in test#b;1: default.
Mmm,
the manual states:
"""
A target also has the ability to perform its execution if (or unless)
a property has been set. This allows, for example, better control on
the building process depending on the state of the system (java
version, OS, command-line property defines, etc.). To make a target
Rainer,
You couldn't be more wrong about the lack of documentation of the non-use of
the ${} notation in if / unless.
The section about targets DOES NOT say that you don't use the ${} notation for
if / unless. It does say this, however:
'This is done by placing the property name between "${"
