To expand on the possible syntax to applying this filters concept at the
resolve level rather than the post-resolve level, you could have in the
module descriptor XML schema a filters element that follows configurations:
Then you'd be adding a filters attribute to the elements that current
Shawn, this feature request is subtly different from configuration
intersection in that it's being specified on the depended-upon module rather
than on the dependent, which is the case with configuration intersection.
Remember last year there had been some discussion of introducing
configuration i
If I am understanding your question correctly, this is already supported by IVY
with the addition of configuration intersection. I requested this feature last
year and Xavier added it last year. You specify multiple configurations for
each "dimension" or "axis" and you can intersect those "dim
It is caused by the way you configured the repository you use for
publishing. I ran into the same issue, where Ivy is using the
"latest.integration" revision of a given dependency with no regards to the
branch even if I've specified one. Then, if that "latest.integration"
happened to be from anot
The following is also on my wishlist. Declare an artifact such as:
and be able to do a resolve or a cachefileset with syntax similar to the
following:
Juha Ranta wrote:
>
>
>
> Juha Ranta wrote:
>>
>>
>>
>> dek577 wrote:
>>>
>>> Does the ivy:retrieve ant task support more advance
Juha, suppose you have an mymbeansmodule ivy.xml with the following
passages:
Then in your module that depends on mbeansmodule, you would have a
dependency:
The dev-only+mbeantypes configuration intersection will only get
dev-only-or-mbeans.jar and not the other two jars. Does this work fo
On Thu 2010-03-04 at 10:44h, Juha Ranta wrote on ivy-user:
:
> Now that I thought of it, I'd like it if I could do something like this:
>
> e:localdir="mbeantypes"/>
>
> and then use the localdir or whatever extra attribute I defined in the
> dependency in my retrieve task.
>
> I don't think i
Juha Ranta wrote:
>
>
>
> dek577 wrote:
>>
>> Does the ivy:retrieve ant task support more advanced configuration
>> specifications similar to the configuration mappings, intersections, and
>> negations described here:
>> http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.h
dek577 wrote:
>
> Does the ivy:retrieve ant task support more advanced configuration
> specifications similar to the configuration mappings, intersections, and
> negations described here:
> http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.html
>
> I'm interested in doing a
I chose checking the ivysettings files into an SCM repo "buildtools" so that I
could recreate a past build if ever needed. If you don't version them, you
don't know what state they were in at the time a build took place. We can
store the subversion repo number of our ivysettings repo "buildtoo
I changed all javac and junit calls to have fork='true'. I have run the
build several times now without encountering the error. Hopefully this has
fixed it. Thank you.
Prior to this suggestion, I was investigating the setting. If you
define a separate resolutionCache and repositoryCache, what is
Another possibility might be that you use the javac task unforked.
This might keep a lock on the jars.
Maarten
- Original Message
From: Troy Self
To: ivy-user@ant.apache.org
Sent: Wed, March 3, 2010 11:20:07 PM
Subject: RE: Cannot delete outdated artifacts in cache
That was my first
Obviously I mean transitive wherever I write transient... Doh!
/axl
> -Original Message-
> From: Andreas Axelsson [mailto:andreas.axels...@combination.se]
> Sent: den 4 mars 2010 09:34
> To: ivy-user@ant.apache.org
> Subject: Partial transient resolve?
>
> I've got some modules which are
I've got some modules which are only required during development and I would
like to mark them as such so that they are not pulled in as transient
dependencies even if a project asks for them.
Example:
A depends on B, always
B depends on C, always
B depends on D, but only during development
Ru
14 matches
Mail list logo