Hi,
As you have noticed I've prepared a maven 2 friendly distribution of Ivy.
Are you ok if we push it (once the release will be accepted) to the apache
maven 2 repository? If so, where is it on people.a.o?
Xavier
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant
On Dec 7, 2007 6:33 AM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> "Xavier Hanin" <[EMAIL PROTECTED]> writes:
>
> > Download the 2.0.0 alpha 2 release files at:
> > http://ant.apache.org/ivy/download.html
>
> This page doesn't support our mirror infrastructure. You should
> replace the link with
> -Original Message-
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 07, 2007 5:25 PM
> To: Ant Developers List
> Subject: Re: extra attributes on publication artifacts
>
> It's a problem for fixing IVY-471 where I only want to write the extra-
> attributes for the
It's a problem for fixing IVY-471 where I only want to write the
extra-attributes for the published artifact that are really defined for that
artifact (and not inherited from the module). In addition, I think it could
confuse people when they define extra-attributes on the module and on the
art
I guess it's more related to IVY-419 (which has been introduced for maven 2
classifers, but is now an Ivy feature).
IVY-419 let people define artifacts for a dependency even though the dependendy
already has a module descriptor. But maybe adding extra attributes the the
ArtifactRevisionId was o
No tests are failing if I remove it. The corresponding svn commit log where
this code has been added is this (svn revision 515753)
NEW: define artifacts not declared by the dependency module descriptor (IVY-419)
FIX: Ivy doesn't recognize maven2 classifiers (IVY-418)
Xavier: could you remember s
I think it is useful to use them in patterns. Try removing this piece of code
and see if a test case is failing, I wouldn't be surprised we have a test case
for that.
Xavier
> -Original Message-
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 07, 2007 4:41 PM
>
Hi,
In the ArtifactRevisionId.newInstance(...) methods, the extra attributes of the
module are automatically added to the extra attributes of the module artifacts.
Any idea what could be the reason for this?
Maarten
_
I don't have either on the box I'm using right now, so I can't make the update
before later this week-end, not sure when actually.
I don't know if you're on a personnal box or not, and what kind of OS you have
(java6 on mac is a problem), but if you can you should install those, it
doesn't take
I don't have Ant 1.7 and java 6 (I know: shame on me... *blush*)
Maarten
- Original Message
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List
Sent: Friday, December 7, 2007 9:46:22 PM
Subject: RE: ivy.xsd outdated
> -Original Message-
> From: Maarten Coene [mailto
> -Original Message-
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 07, 2007 3:41 PM
> To: ant-dev
> Subject: ivy.xsd outdated
>
> The ivy.xsd on the site is not up-to-date:
> http://ant.apache.org/ivy/schemas/ivy.xsd
> (it doesn't support the global exclude elemen
It makes sense. But we still need to stop the graph visit when we find we hit
the same node twice in the same path to avoid a StackOverflow.
Xavier
> -Original Message-
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 07, 2007 3:34 PM
> To: dev@ant.apache.org
> Su
The ivy.xsd on the site is not up-to-date:
http://ant.apache.org/ivy/schemas/ivy.xsd
(it doesn't support the global exclude element)
Can someone update this?
Maarten
Be a better friend, newshound, and
Why not delay the circular dependency check untill the resolve is finished?
Maybe the module causing the circular dependency gets evicted so there might be
no problem at all?
Maarten
- Original Message
From: Xavier Hanin (JIRA) <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Friday, Dec
Hi,
I've started thinking at how to implement IVY-658, and it's not that easy to
get information necessary to clean a repository intelligently.
To do so, we need to have information about the dependers of a module. If Ivy
shines at finding dependees, it provides no way to access dependers, so t
I tried to test it a few time from the command line with only that test and in
those case it works.
It is only when I run all of them that I have the issue.
I suspect it might be triggered by the garbage collector put some load at the
wrong moment.
I hope it will be reproducible with tracing en
On Dec 7, 2007 10:12 AM, Gilles Scokart <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I got this when running ant test:
>
>
>
> name="testConcurrentResolve" time="16.312">
>
>junit.framework
>
> .AssertionFailedError: expected:<10> but was:<9>
>
>at
> org.apache.ivy.plugins.lock.ArtifactLockS
+1
Gilles
> -Original Message-
> From: Xavier Hanin [mailto:[EMAIL PROTECTED]
> Sent: jeudi 6 décembre 2007 7:34
> To: Ant Developers List
> Subject: [VOTE] Release Ivy 2.0.0-beta1 (second attempt)
>
> I have built a new release candidate for Ivy 2.0.0-beta1
>
> You can download it from
I got this when running ant test:
junit.framework
.AssertionFailedError: expected:<10> but was:<9>
at
org.apache.ivy.plugins.lock.ArtifactLockStrategyTest.testConcurrentResolve(ArtifactLockStrategyTest.java:72)
The second time, I got this :
junit.framewor
19 matches
Mail list logo
