Re: [VOTE] Merge Ivy and Ant Dev Lists

[Maarten Coene]

+1

Maarten

- Original Message 
From: Stefan Bodewig <[EMAIL PROTECTED]>
To: dev@ant.apache.org; [EMAIL PROTECTED]
Sent: Friday, October 26, 2007 6:18:41 AM
Subject: [VOTE] Merge Ivy and Ant Dev Lists


Hi,

it seemed as if the discussion favored a joined mailing lists of Anf
(and antlibs) and Ivy, so here is the formal vote.

Should we merge [EMAIL PROTECTED] into [EMAIL PROTECTED] and likewise
[EMAIL PROTECTED] into the new [EMAIL PROTECTED]

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ivy-dev list migration

[Maarten Coene]

+1 for asking people to re-subscribe

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, December 5, 2007 10:56:59 AM
Subject: Re: ivy-dev list migration


On Dec 5, 2007 8:55 AM, Gilles Scokart <[EMAIL PROTECTED]> wrote:

>
> > I'm leaning towards asking people to re-subscribe here manually and
> > deal with the ivy-dev list the same way we intend to do for
> > ivy.commits or ivy-private (i.e. forward mails sent there).
>
> +1
> I think it would be better to ask people to re-subscribe.  It is
> [theoretically] true that some people that subscribed
> to ivy-dev at incubator may not want to be subscribed to dev at ant.

+1

Xavier





  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Ivy 2.0.0-beta1

[Maarten Coene]

+1 for updating makepom and merging svn revision r601489 into this beta release.

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, December 5, 2007 8:53:30 PM
Subject: RE: [VOTE] Release Ivy 2.0.0-beta1


> -Original Message-
> From: Gilles Scokart [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 05, 2007 8:54 AM
> To: 'Ant Developers List'
> Subject: RE: [VOTE] Release Ivy 2.0.0-beta1
>
>
> The pom.xml should start with the usual apache header to indicate
 that
> the pom itself is licensed under Apache license.
> There was a discussion some weeks ago that suggest it is a good
> practice.
Indeed, sounds like a good change to make. Since this pom is generated
 using makepom, I guess we'll have to make some changes to makepom too.

>
> Also in the pom, I think it would be better to use
> true rather than just .
Ok, I didn't know that, but if we need to update the pom (and makepom)
 let's update this too.

>
>
> By the way, did someone already run RAT against it?
I didn't.

BTW, if we need to make an update to the release, what do you think of
 merging the FIX I've just commited on trunk (svn revision 601489)? It's
 fixing some concurrency issues found with the new cache locking
 mechanism, I've now made more tests in real life in a pretty high concurrency
 use case (hundreds of modules, tens of concurrent processes on tens of
 machines, all using the same cache) and it's working well... with this
 fix.

Xavier

>
> Gilles
>
> > -Original Message-
> > From: Xavier Hanin [mailto:[EMAIL PROTECTED]
> > Sent: mercredi 5 décembre 2007 3:13
> > To: Ant Developers List
> > Subject: [VOTE] Release Ivy 2.0.0-beta1
> >
> > I have built a release candidate for Ivy 2.0.0-beta1
> >
> > You can download it from this URL:
> > http://people.apache.org/~xavier/ivy/staging/2.0.0-beta1/
> >
> > Do you vote for the release of these binaries?
> >
> > [ ] Yes
> > [ ] No
> >
> > Regards,
> >
> > Xavier, Ivy 2.0.0-beta1 release manager
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > http://xhab.blogspot.com/
> > http://ant.apache.org/ivy/
> > http://www.xoocode.org/
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release Ivy 2.0.0-beta1 (second attempt)

[Maarten Coene]

+1

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, December 6, 2007 7:34:11 AM
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 this URL:
http://people.apache.org/~xavier/ivy/staging/2.0.0-beta1/


and the m2 repository is here:
http://people.apache.org/~xavier/m2-staging-repo/

Compared to the previous release attempt I've only the following
 changes
(which can be tracked in svn in the 2.0.0-beta1 branch):
- merged a fix on cache locking (disabled by default)
- merged some changes in makepom task to address Gilles remark
- fix a bug on a unit test of makepom not done on trunk (still need to
 be
merged to trunk)
- reflect change to makepomin build-release.xml
- package readme with all ditribs (including crypto notice)
- put maven 2 distrib in a m2 staging repo for ease of testing

I haven't done much testing of these artifacts, I had some slight
 troubles
getting in my way (but when it takes 10 min to make a full release
 build a
slight error can make you loose a lot of time), and it's getting really
 late
over here, but I don't expect to have any more time for a new release
attempt until next week, so if ever this one doesn't pass, I hope
 someone
will step up to replace me as release mgr for this release.

So, do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Xavier, Ivy 2.0.0-beta1 release manager



-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

LatestConflictManagerTest fails

[Maarten Coene]

Hi,

The LatestConflictManagerTest fails on my fresh copy of svn trunk. However, it 
doesn't fail on gump. Anyone an idea?

I get the following exception when running in Eclipse (all tests fail with 
similar error, except the first one)
java.lang.IllegalArgumentException: invalid micro ivy format: #A;1-> { #B;1.4 
#C;[2.0,2.5] }
at org.apache.ivy.TestHelper.parseMicroIvyDescriptor(TestHelper.java:168)
at org.apache.ivy.TestFixture.addMD(TestFixture.java:82)
at 
org.apache.ivy.plugins.conflict.LatestCompatibleConflictManagerTest.testCompatibilityResolve1(LatestCompatibleConflictManagerTest.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at 
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

Maarten





  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: LatestConflictManagerTest fails

[Maarten Coene]

I run my tests with JDK 1.4, maybe the regular expression handling is different?
I'll try to debug, but for the moment, I'm trying to understand this new syntax 
(or maybe it's just too late in the evening for this)

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, December 6, 2007 11:32:28 PM
Subject: RE: LatestConflictManagerTest fails


It's strange. Try to go in debug mode and see what happens with the
 third matcher in TestHelper#parseMicroIvyDescriptor.
Oh, and since we are using a constant for the pattern, are you sure you
 cleaned your build before running (you say you have a fresh copy, so I
 don't see how it cold be an issue... but anyway).

Xavier

> -Original Message-
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 06, 2007 5:28 PM
> To: dev@ant.apache.org
> Subject: LatestConflictManagerTest fails
>
> Hi,
>
> The LatestConflictManagerTest fails on my fresh copy of svn trunk.
> However, it doesn't fail on gump. Anyone an idea?
>
> I get the following exception when running in Eclipse (all tests fail
> with similar error, except the first one)
> java.lang.IllegalArgumentException: invalid micro ivy format: #A;1->
 {
> #B;1.4 #C;[2.0,2.5] }
> at
>
 org.apache.ivy.TestHelper.parseMicroIvyDescriptor(TestHelper.java:168)
> at org.apache.ivy.TestFixture.addMD(TestFixture.java:82)
> at
>
 org.apache.ivy.plugins.conflict.LatestCompatibleConflictManagerTest.tes
> tCompatibilityResolve1(LatestCompatibleConflictManagerTest.java:55)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
 Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at junit.framework.TestCase.runTest(TestCase.java:164)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:120)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at
>
 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JU
> nit3TestReference.java:130)
> at
>
 org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.j
> ava:38)
> at
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteT
> estRunner.java:460)
> at
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteT
> estRunner.java:673)
> at
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRu
> nner.java:386)
> at
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestR
> unner.java:196)
>
> Maarten
>
>
>
>
>
>
>
 ___
> _
> Looking for last minute shopping deals?
> Find them fast with Yahoo! Search.
>
 http://tools.search.yahoo.com/newsearch/category.php?category=shopping
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: LatestConflictManagerTest fails

[Maarten Coene]

I've found it. The Pattern.toString() method doesn't return the String pattern 
on JDK 1.4. Maybe this is different on JDK 1.5+?

Maarten

- Original Message ----
From: Maarten Coene <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, December 6, 2007 11:37:23 PM
Subject: Re: LatestConflictManagerTest fails


I run my tests with JDK 1.4, maybe the regular expression handling is
 different?
I'll try to debug, but for the moment, I'm trying to understand this
 new syntax (or maybe it's just too late in the evening for this)

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, December 6, 2007 11:32:28 PM
Subject: RE: LatestConflictManagerTest fails


It's strange. Try to go in debug mode and see what happens with the
 third matcher in TestHelper#parseMicroIvyDescriptor.
Oh, and since we are using a constant for the pattern, are you sure you
 cleaned your build before running (you say you have a fresh copy, so I
 don't see how it cold be an issue... but anyway).

Xavier

> -Original Message-
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 06, 2007 5:28 PM
> To: dev@ant.apache.org
> Subject: LatestConflictManagerTest fails
>
> Hi,
>
> The LatestConflictManagerTest fails on my fresh copy of svn trunk.
> However, it doesn't fail on gump. Anyone an idea?
>
> I get the following exception when running in Eclipse (all tests fail
> with similar error, except the first one)
> java.lang.IllegalArgumentException: invalid micro ivy format: #A;1->
 {
> #B;1.4 #C;[2.0,2.5] }
> at
>
 org.apache.ivy.TestHelper.parseMicroIvyDescriptor(TestHelper.java:168)
> at org.apache.ivy.TestFixture.addMD(TestFixture.java:82)
> at
>

 org.apache.ivy.plugins.conflict.LatestCompatibleConflictManagerTest.tes
> tCompatibilityResolve1(LatestCompatibleConflictManagerTest.java:55)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
 Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at junit.framework.TestCase.runTest(TestCase.java:164)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:120)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at
>

 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JU
> nit3TestReference.java:130)
> at
>

 org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.j
> ava:38)
> at
>

 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteT
> estRunner.java:460)
> at
>

 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteT
> estRunner.java:673)
> at
>

 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRu
> nner.java:386)
> at
>

 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestR
> unner.java:196)
>
> Maarten
>
>
>
>
>
>
>

 ___
> _
> Looking for last minute shopping deals?
> Find them fast with Yahoo! Search.
>
 http://tools.search.yahoo.com/newsearch/category.php?category=shopping
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.
  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: LatestConflictManagerTest fails

[Maarten Coene]

No this shouldn't block the beta release indeed!

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, December 6, 2007 11:49:30 PM
Subject: RE: LatestConflictManagerTest fails


Ok... yes on jdk 5 and 6 it's different, it works :-). But the problem
 is only for tests, so we know we have one test failing with jdk 1.4 for
 2.0 beta 1, doesn't sound like a showstopper issue for me.

Xavier

> -Original Message-----
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 06, 2007 5:46 PM
> To: Ant Developers List
> Subject: Re: LatestConflictManagerTest fails
>
> I've found it. The Pattern.toString() method doesn't return the
 String
> pattern on JDK 1.4. Maybe this is different on JDK 1.5+?
>
> Maarten
>
> - Original Message 
> From: Maarten Coene <[EMAIL PROTECTED]>
> To: Ant Developers List 
> Sent: Thursday, December 6, 2007 11:37:23 PM
> Subject: Re: LatestConflictManagerTest fails
>
>
> I run my tests with JDK 1.4, maybe the regular expression handling is
>  different?
> I'll try to debug, but for the moment, I'm trying to understand this
>  new syntax (or maybe it's just too late in the evening for this)
>
> Maarten
>
> - Original Message 
> From: Xavier Hanin <[EMAIL PROTECTED]>
> To: Ant Developers List 
> Sent: Thursday, December 6, 2007 11:32:28 PM
> Subject: RE: LatestConflictManagerTest fails
>
>
> It's strange. Try to go in debug mode and see what happens with the
>  third matcher in TestHelper#parseMicroIvyDescriptor.
> Oh, and since we are using a constant for the pattern, are you sure
 you
>  cleaned your build before running (you say you have a fresh copy, so
 I
>  don't see how it cold be an issue... but anyway).
>
> Xavier
>
> > -Original Message-
> > From: Maarten Coene [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, December 06, 2007 5:28 PM
> > To: dev@ant.apache.org
> > Subject: LatestConflictManagerTest fails
> >
> > Hi,
> >
> > The LatestConflictManagerTest fails on my fresh copy of svn trunk.
> > However, it doesn't fail on gump. Anyone an idea?
> >
> > I get the following exception when running in Eclipse (all tests
 fail
> > with similar error, except the first one)
> > java.lang.IllegalArgumentException: invalid micro ivy format:
 #A;1->
>  {
> > #B;1.4 #C;[2.0,2.5] }
> > at
> >
>
  org.apache.ivy.TestHelper.parseMicroIvyDescriptor(TestHelper.java:168)
> > at org.apache.ivy.TestFixture.addMD(TestFixture.java:82)
> > at
> >
>
>
>
 org.apache.ivy.plugins.conflict.LatestCompatibleConflictManagerTest.tes
> > tCompatibilityResolve1(LatestCompatibleConflictManagerTest.java:55)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>  Source)
> > at java.lang.reflect.Method.invoke(Unknown Source)
> > at junit.framework.TestCase.runTest(TestCase.java:164)
> > at junit.framework.TestCase.runBare(TestCase.java:130)
> > at junit.framework.TestResult$1.protect(TestResult.java:106)
> > at junit.framework.TestResult.runProtected(TestResult.java:124)
> > at junit.framework.TestResult.run(TestResult.java:109)
> > at junit.framework.TestCase.run(TestCase.java:120)
> > at junit.framework.TestSuite.runTest(TestSuite.java:230)
> > at junit.framework.TestSuite.run(TestSuite.java:225)
> > at
> >
>
>
>
 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JU
> > nit3TestReference.java:130)
> > at
> >
>
>
>
 org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.j
> > ava:38)
> > at
> >
>
>
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteT
> > estRunner.java:460)
> > at
> >
>
>
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteT
> > estRunner.java:673)
> > at
> >
>
>
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRu
> > nner.java:386)
> > at
> >
>
>
>
 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestR
> > unner.java:196)
> >
> > Maarten
> >
> >
> >
> >
> >
> >
> >
>
>
>
 ___
> > _
> > Looking for last minute shopping deals?
> > F

Re: ivy.xsd outdated

[Maarten Coene]

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:[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 element)
>
> Can someone update this?
Can't you? All you need is to check out
 https://svn.apache.org/repos/asf/ant/ivy/site/, update schemas/ivy.xsd,
 and call ant publish-site in the site directory you checked out... if
 you have ant 1.7, java 6 and remember your people.apache.org account it
 should be very straightforward.

Xavier

>
> Maarten
>
>
>
>
>
>
 ___
> _
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile.  Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

ivy.xsd outdated

[Maarten Coene]

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 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

extra attributes on publication artifacts

[Maarten Coene]

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




  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: extra attributes on publication artifacts

[Maarten Coene]

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 
artifact with the same name -> which one will be taken? And at least, at the 
moment, there is a bug in this ArtifactRevisionId.newInstance(...) method which 
causes that the original extra-attributes on the artifact are lost.

But I'll take a look at the example in IVY-418. If that one succeeds, I'll 
remove this piece of code that adds these extra attributes to the artifact, ok?

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Friday, December 7, 2007 11:16:15 PM
Subject: RE: extra attributes on publication artifacts


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 only an attempt which end up being
 unuseful. If no unit test fails, it's probably the reason. But we'd
 need to make a real world test with a dependency on a mven 2 pom using
 classifiers (there's one example in IVY-418).

BTW, is it a source of problem for you?

Xavier


> -Original Message-
> From: Maarten Coene [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 07, 2007 5:04 PM
> To: Ant Developers List
> Subject: Re: extra attributes on publication artifacts
>
> 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 some more details? Maybe something with
> these maven2 classifiers?
>
> Maarten
>
> - Original Message 
> From: Xavier Hanin <[EMAIL PROTECTED]>
> To: Ant Developers List 
> Sent: Friday, December 7, 2007 10:46:56 PM
> Subject: RE: extra attributes on publication artifacts
>
>
> 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
> > To: ant-dev
> > Subject: extra attributes on publication artifacts
> >
> > 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
> >
> >
> >
> >
> >
> >
>
>
 ___
> > _
> > Never miss a thing.  Make Yahoo your home page.
> > http://www.yahoo.com/r/hs
> >
> >
 -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>
>
>
 ___
> _
> Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile.  Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Handling circular dependencies

[Maarten Coene]

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, December 7, 2007 9:22:43 PM
Subject: [jira] Resolved: (IVY-663) latest compatible conflict manager fails 
with circular dependencies and dynamic revision



I've just committed a fix for this, but it slightly changes the way
 circular dependencies are handled, we may have to discuss that further.

The problem is that for the moment we consider we have a circular
 dependency as soon as we find the same module id twice in the visit path. It
 means this happens before any conflict resolution is done, therefore
 letting no chance to a conflict manager to deal with the problem. I
 haven't actually changed this yet, I've only delayed the moment when
 isCircular is checked by the ResolveEngine to know if it has to continue the
 graph visit. But I'm wondering if we shouldn't delay the whole circular
 dependency check (including the call to CircularDependencyStrategy) to
 the moment we have twice the same ModuleRevisionId in the path, and
 not only ModuleId. We should still handle the case of the module
 currently resolved specifically, but I think it makes sense to say that
 #A;1->#B;1->#A;2 is not a circular dependency (this can only happen with a
 conflict manager accepting multiple revisions of the same module).

Thoughts?






  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: extra attributes on publication artifacts

[Maarten Coene]

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 some more details? Maybe something with these maven2 
classifiers?

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Friday, December 7, 2007 10:46:56 PM
Subject: RE: extra attributes on publication artifacts


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
> To: ant-dev
> Subject: extra attributes on publication artifacts
>
> 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
>
>
>
>
>
>
 ___
> _
> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [EMAIL PROTECTED]: Project ivy-tests (in module ivy) failed

[Maarten Coene]

I didn't detect this error because I'm running tests with Java 1.4 where the 
validation of Ivy files doesn't work because the standard XML parser doesn't 
support XML Schema validation. I've added Xerces to the test classpath to avoid 
this in the future, I hope it won't give problems with more recent Java 
versions...

Maarten


- Original Message 
From: Gump Integration Build <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Wednesday, December 12, 2007 7:22:11 PM
Subject: [EMAIL PROTECTED]: Project ivy-tests (in module ivy) failed


To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project ivy-tests has an issue affecting its community integration.
This issue affects 1 projects,
 and has been outstanding for 12 runs.
The current state of this project is 'Failed', with reason 'Build
 Failed'.
For reference only, the following projects are affected by this:
- ivy-tests :  Ivy is a tool for managing (recording, tracking,
 resolving a...


Full details are available at:
http://vmgump.apache.org/gump/public/ivy/ivy-tests/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages)
 were provided:
 -INFO- Failed with reason build failed
 -INFO- Project Reports in:
 /srv/gump/public/workspace/ivy/build/test-report



The following work was performed:
http://vmgump.apache.org/gump/public/ivy/ivy-tests/gump_work/build_ivy_ivy-tests.html
Work Name: build_ivy_ivy-tests (Type: Build)
Work ended in a state of : Failed
Elapsed: 3 mins 58 secs
Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java
 -Djava.awt.headless=true
 
-Xbootclasspath/p:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main
 -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only 
-Doffline=true -Dno.resolve=true test 
[Working Directory: /srv/gump/public/workspace/ivy]
CLASSPATH:
 
/usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ivy/build/test:/srv/gump/public/workspace/ivy/build/artifact/jars/ivy-12122007.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/packages/junit3.8.1/junit.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/httpcomponents/oac.hc3x/dist/commons-httpclient.jar:/srv/gump/public/workspace/apache-commons/codec/dist/commons-codec-12122007.jar:/srv/gump/public/workspace/commons-cli-1.0.x/target/commons-cli-12122007.jar:/srv/gump/public/workspace/jakarta-oro
/jakarta-oro-

 
12122007.jar:/srv/gump/public/workspace/apache-commons/vfs/target/commons-vfs-12122007.jar:/srv/gump/public/workspace/apache-commons/vfs/sandbox/target/commons-vfs-sandbox-12122007.jar:/srv/gump/public/workspace/jakarta-slide/webdavclient/dist/lib/jakarta-slide-webdavlib-12122007.jar:/srv/gump/packages/jsch/jsch-0.1.28.jar:/srv/gump/public/workspace/junit/dist/junit-12122007.jar:/srv/gump/public/workspace/apache-commons/lang/commons-lang-12122007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-12122007.jar:/srv/gump/public/workspace/apache-commons/logging/target/commons-logging-api-12122007.jar:/srv/gump/public/workspace/apache-commons/collections/build/commons-collections-12122007.jar:/srv/gump/public/workspace/commons-sandbox/compress/target/commons-compress-12122007.jar:/srv/gump/public/workspace/apache-commons/net/dist/commons-net-12122007.jar:/
srv/gump/public/workspa

 
ce/httpcomponents/2.0.2/commons-httpclient-2.0.2.jar:/srv/gump/packages/jcifs/jcifs-0.8.1.jar
-
[junit] Tests run: 21, Failures: 0, Errors: 0, Time elapsed: 2,208
 sec
[junit] Running
 org.apache.ivy.plugins.parser.m2.PomModuleDescriptorWriterTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0,623
 sec
[junit] Running
 org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorWriterTest
[junit] , xml parsing:
 
file:/srv/gump/public/workspace/ivy/build/test/org/apache/ivy/plugins/parser/xml/test.xml:41:61:
 cvc-complex-type.3.2.2: Attribute 'attr2' is not allowed to appear in element 
'conf'. in
 
file:/srv/gump/public/workspace/ivy/build/test/org/apache/ivy/plugins/parser/xml/test.xml
[junit] , xml parsing:
 
file:/srv/gump/public/workspace/ivy/build/test/org/apache/ivy/plugins/parse

Re: ivy download page

[Maarten Coene]

It seems there is a trick to view the site before it has being rsync'ed by 
using a HTTP proxy:
http://www.apache.org/dev/project-site.html

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, December 13, 2007 6:45:27 PM
Subject: Re: ivy download page


BTW, is there a way to make modifications directly to the web site or
 force
a sync from people.a.o? It can be very annoying to have one hour cycles
 when
testing site stuff.

Xavier

On Dec 13, 2007 6:41 PM, Xavier Hanin <[EMAIL PROTECTED]> wrote:

> Hi,
>
> I've just updated the public Ivy web site, and the download page with
> mirror stuff is not working properly yet. My guess is that the
 problem is
> that the cgi was not marked as executable, which I've fixed, but I
 can't be
> sure it works since I have to wait for the next sync to happen.
>
> If it doesn't work, it would be nice if somebody else would have a
 look
> since I won't be online much until tomorrow.
>
> BTW, the way we publish ivy site do not support executable flag
 setting
> yet, so don't update the site with ant publish-site.
>
> Xavier
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/




-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ivy download page

[Maarten Coene]

The download page is working now :-)
I've played a bit with the download.cgi file, but I don't know what was the 
magical change that made things work, maybe someone else did a change as well???

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Friday, December 14, 2007 6:41:08 PM
Subject: Re: ivy download page


On Dec 14, 2007 2:02 PM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:

> "Xavier Hanin" <[EMAIL PROTECTED]> writes:
>
> > Thanks. The proxy trick to access directly the site seems to work,
 but I
> > still have the 500 error and seem to have no access to
> > www.apache.orgmachine to get access to the logs.
>
> Neither have I.
>
> Since you get the error when using the "proxy trick", you only need
 to
> llok into the logs on minotaur. It says
>
>  File "/www/www.apache.org/dyn/mirrors/mirrors.cgi", line 29, in
 
>import GeoIP
> ImportError: No module named GeoIP
>
> Ant's onw download pages don't work via the proxy either, I guess the
> GeoIP module is not installed on minotaur so the CGIs don't work
 there
> - but they do work on the production sites.  Maybe it really just is
 a
> matter of waiting a bit longer.

Ok, so it seems we'll get stuck with one hour cycles to find the
 solution,
and with no access to the logs... I'm not proficient with python at all
neither with cgi, so I wonder if I'll be able to find the fix. It seems
 the
python script doesn't like something in our download.html, but what?
 I'll
try to figure it out but I won't have much time this week-end, so if
 anyone
beats me on this I'd be more than happy :-)

>
>
> > BTW I've changed the right for download.cgi and download.html, you
> should be
> > able to make changes.
>
> All the files in /ivy should be group writable on minotaur.  Please
> adjust your umask or run an explicit chmod after syncing the site up
 to
> it.

Sure, I'll do.

Xavier

>
>
> Stefan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: ivy download page

[Maarten Coene]

The download page isn't working again (Internal Server Error).
I've noticed some strange characters in the download.cgi file. I've deleted 
them, lets hope this solves the problem.

Maarten


- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Saturday, December 15, 2007 11:02:01 AM
Subject: Re: ivy download page


On Dec 14, 2007 10:58 PM, Maarten Coene <[EMAIL PROTECTED]>
 wrote:

> The download page is working now :-)
> I've played a bit with the download.cgi file, but I don't know what
 was
> the magical change that made things work, maybe someone else did a
 change as
> well???

I thought I did the fix, but I'm not sure it's really what I've done
 either.
What seemed to be a problem for the python script was the use of square
brackets in the download.html in a javascript source redirecting to
download.cgi from download.html. I've externalized the script to a
 separate
file (on people.a.o only, still have to update the site source). What
 is
nice is that it now works, whatever the reason is.

I'll make the announcement on mailing lists today, but I'll wait monday
 to
make the announcement on the web, it will increase our chance to be
 seen.

Xavier

>
>
> Maarten
>
> - Original Message 
> From: Xavier Hanin <[EMAIL PROTECTED]>
> To: Ant Developers List 
> Sent: Friday, December 14, 2007 6:41:08 PM
> Subject: Re: ivy download page
>
>
> On Dec 14, 2007 2:02 PM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>
> > "Xavier Hanin" <[EMAIL PROTECTED]> writes:
> >
> > > Thanks. The proxy trick to access directly the site seems to
 work,
>  but I
> > > still have the 500 error and seem to have no access to
> > > www.apache.orgmachine to get access to the logs.
> >
> > Neither have I.
> >
> > Since you get the error when using the "proxy trick", you only need
>  to
> > llok into the logs on minotaur. It says
> >
> >  File "/www/www.apache.org/dyn/mirrors/mirrors.cgi", line 29, in
>  
> >import GeoIP
> > ImportError: No module named GeoIP
> >
> > Ant's onw download pages don't work via the proxy either, I guess
 the
> > GeoIP module is not installed on minotaur so the CGIs don't work
>  there
> > - but they do work on the production sites.  Maybe it really just
 is
>  a
> > matter of waiting a bit longer.
>
> Ok, so it seems we'll get stuck with one hour cycles to find the
>  solution,
> and with no access to the logs... I'm not proficient with python at
 all
> neither with cgi, so I wonder if I'll be able to find the fix. It
 seems
>  the
> python script doesn't like something in our download.html, but what?
>  I'll
> try to figure it out but I won't have much time this week-end, so if
>  anyone
> beats me on this I'd be more than happy :-)
>
> >
> >
> > > BTW I've changed the right for download.cgi and download.html,
 you
> > should be
> > > able to make changes.
> >
> > All the files in /ivy should be group writable on minotaur.  Please
> > adjust your umask or run an explicit chmod after syncing the site
 up
>  to
> > it.
>
> Sure, I'll do.
>
> Xavier
>
> >
> >
> > Stefan
> >
> >
 -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://ant.apache.org/ivy/
> http://www.xoocode.org/
>
>
>
>
>
>
>
  

> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy web site

[Maarten Coene]

I'd prefer having the site in SVN too...
btw, the rights on the /www/ant.apache.org/ivy directory aren't correct, I 
can't create new files in it. Could you update that?

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Saturday, December 15, 2007 11:40:10 AM
Subject: Ivy web site


Hi,

The problem for the download page is now fixed, but it has raised some
questions about how we manage our web site:
- we are not in sync with what the apache documentation says on how to
manage web sites [1]. We should put generated site in svn to comply
- by uploading the generated web site, we do not support the executable
 flag
which is a problem for download.cgi
- uploading the whole site takes a long time sometimes for small
 changes
only, using svn would rely on diff only which would make the "upload"
 (would
be a commit actually) more efficient.

Hence I'm in favor of storing the result of site generation in svn and
checkout this result on people.a.o for the web site. Making changes to
 the
site would still be done to the site source, and a generation
 (requiring ant
1.7 and java 6) would still be necessary.

WDYT?

Xavier

[1] http://www.apache.org/dev/project-site.html

-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ivy trunk doesn't compile

[Maarten Coene]

I receive the following error when compiling the latest Ivy sources from SVN. 
Xavier: could this be introduced somewhere with your recent changes?

java.lang.RuntimeException: problem during retrieve of org.apache.ivy#ivy: 
java.lang.ClassCastException
at 
org.apache.ivy.core.retrieve.RetrieveEngine.retrieve(RetrieveEngine.java:175)
at org.apache.ivy.Ivy.retrieve(Ivy.java:535)
at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:50)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:275)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at org.apache.tools.ant.Target.performTasks(Target.java:369)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
at org.apache.tools.ant.Main.runBuild(Main.java:668)
at org.apache.tools.ant.Main.startAnt(Main.java:187)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
Caused by: java.lang.ClassCastException
at 
org.apache.ivy.core.retrieve.RetrieveEngine$1.compare(RetrieveEngine.java:356)
at java.util.Arrays.mergeSort(Arrays.java:1278)
at java.util.Arrays.sort(Arrays.java:1219)
at java.util.Collections.sort(Collections.java:155)
at 
org.apache.ivy.core.retrieve.RetrieveEngine.determineArtifactsToCopy(RetrieveEngine.java:310)
at 
org.apache.ivy.core.retrieve.RetrieveEngine.retrieve(RetrieveEngine.java:95)
... 15 more

Maarten




  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r608922 - in /ant/ivy/core/trunk: ./ doc/configuration/ src/java/org/apache/ivy/core/ src/java/org/apache/ivy/core/cache/ src/java/org/apache/ivy/core/check/ src/java/org/apache/ivy/co

[Maarten Coene]

Xavier,

why did you change the way the attributes are processed in the 
XmlSettingsParser class?

For instance, before your commit, it was like this:
String propFilePath = ivy.substitute((String) attributes.get("file"));
After your commit, it is like this:
String propFilePath = (String) attributes.get("file");

I might have missed something, but doesn't this give problems when you use 
variables in your settings file, for instance:



Maarten

- Original Message 
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Friday, January 4, 2008 6:05:57 PM
Subject: svn commit: r608922 - in /ant/ivy/core/trunk: ./ doc/configuration/ 
src/java/org/apache/ivy/core/ src/java/org/apache/ivy/core/cache/ 
src/java/org/apache/ivy/core/check/ src/java/org/apache/ivy/core/repository/ 
src/java/org/apache/ivy/core/resolve/ src...

Author: xavier
Date: Fri Jan  4 09:05:55 2008
New Revision: 608922

URL: http://svn.apache.org/viewvc?rev=608922&view=rev
Log:
IMPROVEMENT: use ModuleRevisionId instead of ModuleId in
 IvySettings#getResolver (IVY-591)

[...]

Modified:
 ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/XmlSettingsParser.java
URL:
 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/XmlSettingsParser.java?rev=608922&r1=608921&r2=608922&view=diff
==
---
 
ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/XmlSettingsParser.java 
(original)
+++
 
ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/XmlSettingsParser.java 
Fri Jan  4 09:05:55 2008
@@ -30,8 +30,8 @@
 
 import javax.xml.parsers.SAXParserFactory;
 
+import org.apache.ivy.core.IvyPatternHelper;
 import org.apache.ivy.core.cache.RepositoryCacheManager;
-import org.apache.ivy.core.module.id.ModuleId;
 import org.apache.ivy.core.module.status.StatusManager;
 import org.apache.ivy.plugins.circular.CircularDependencyStrategy;
 import org.apache.ivy.plugins.conflict.ConflictManager;
@@ -125,7 +125,7 @@
 // we first copy attributes in a Map to be able to modify them
 Map attributes = new HashMap();
 for (int i = 0; i < att.getLength(); i++) {
-attributes.put(att.getQName(i), att.getValue(i));
+attributes.put(att.getQName(i),
 ivy.substitute(att.getValue(i)));
 }
 
 try {
@@ -183,15 +183,15 @@
 configurator.startCreateChild(qName);
 for (Iterator iter =
 attributes.keySet().iterator(); iter.hasNext();) {
 String attName = (String) iter.next();
-configurator.setAttribute(attName,
 ivy.substitute((String) attributes
-.get(attName)));
+configurator.setAttribute(attName, (String)
 attributes
+.get(attName));
 }
 }
 } else if ("classpath".equals(qName)) {
-String urlStr = ivy.substitute((String)
 attributes.get("url"));
+String urlStr = (String) attributes.get("url");
 URL url = null;
 if (urlStr == null) {
-String file = ivy.substitute((String)
 attributes.get("file"));
+String file = (String) attributes.get("file");
 if (file == null) {
 throw new IllegalArgumentException(
 "either url or file should be given
 for classpath element");
@@ -203,14 +203,14 @@
 }
 ivy.addClasspathURL(url);
 } else if ("typedef".equals(qName)) {
-String name = ivy.substitute((String)
 attributes.get("name"));
-String className = ivy.substitute((String)
 attributes.get("classname"));
+String name = (String) attributes.get("name");
+String className = (String)
 attributes.get("classname");
 Class clazz = ivy.typeDef(name, className);
 configurator.typeDef(name, clazz);
 } else if ("property".equals(qName)) {
-String name = ivy.substitute((String)
 attributes.get("name"));
-String value = ivy.substitute((String)
 attributes.get("value"));
-String override = ivy.substitute((String)
 attributes.get("override"));
+String name = (String) attributes.get("name");
+String value = (String) attributes.get("value");
+String override = (String) attributes.get("override");
 if (name == null) {
 throw new IllegalArgumentException("missing
 attribute name on property tag");
 }
@@ -220,8 +220,8 @@
 ivy.setVariable(name, value, override == null ? true :
 Boolean.valueOf(override)
 .booleanValue());
 } else if ("properties".equals(qName)) {
- 

Re: svn commit: r610562 - in /ant/ivy/core/trunk: ./ src/java/org/apache/ivy/ant/ src/java/org/apache/ivy/core/ src/java/org/apache/ivy/core/retrieve/ src/java/org/apache/ivy/core/settings/ test/java/

[Maarten Coene]

Strange,
I tested it with a sun jdk 1.4.2 (I can't check the patch level from here) and 
it was working ok, so I assumed it would work for all sun 1.4.2 VM's :-( 

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Thursday, January 10, 2008 11:58:58 AM
Subject: Re: svn commit: r610562 - in /ant/ivy/core/trunk: ./ 
src/java/org/apache/ivy/ant/ src/java/org/apache/ivy/core/ 
src/java/org/apache/ivy/core/retrieve/ src/java/org/apache/ivy/core/settings/ 
test/java/org/apache/ivy/ant/


On Jan 9, 2008 10:03 PM, <[EMAIL PROTECTED]> wrote:

> Author: maartenc
> Date: Wed Jan  9 13:02:58 2008
> New Revision: 610562
>
> URL: http://svn.apache.org/viewvc?rev=610562&view=rev
> Log:
> NEW: Add support for importing environment variables (IVY-608)

[...]

> Modified:
>
 
ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/IvyVariableContainerImpl.java
> URL:
>
 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/IvyVariableContainerImpl.java?rev=610562&r1=610561&r2=610562&view=diff
>
>
 ==
> ---
>
 
ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/IvyVariableContainerImpl.java
> (original)
> +++
>
 
ant/ivy/core/trunk/src/java/org/apache/ivy/core/settings/IvyVariableContainerImpl.java
> Wed Jan  9 13:02:58 2008
> @@ -25,8 +25,17 @@
>
>  public class IvyVariableContainerImpl implements
 IvyVariableContainer {
>
> -private HashMap variables = new HashMap();
> +private Map variables;
> +private String envPrefix;
>
> +public IvyVariableContainerImpl() {
> +this.variables = new HashMap();
> +}
> +
> +public IvyVariableContainerImpl(Map variables) {
> +this.variables = variables;
> +}
> +
> /*
>  * (non-Javadoc)
>  *
> @@ -40,21 +49,27 @@
> } else {
> Message.debug("'" + varName + "' already set: discarding
 '" +
> value + "'");
> }
> -
> +}
> +
> +public void setEnvironmentPrefix(String prefix) {
> +if ((prefix != null) && !prefix.endsWith(".")) {
> +this.envPrefix = prefix + ".";
> +} else {
> +this.envPrefix = prefix;
> +}
> }
>
> private String substitute(String value) {
> -return IvyPatternHelper.substituteVariables(value,
> getVariables());
> +return IvyPatternHelper.substituteVariables(value, this);
> }
>
> -/*
> - * (non-Javadoc)
> - *
> - * @see
> org.apache.ivy.core.settings.IvyVariableContainer#getVariables()
> - */
> -public Map getVariables() {
> +protected Map getVariables() {
> return variables;
> }
> +
> +protected String getEnvironmentPrefix() {
> +return envPrefix;
> +}
>
> /*
>  * (non-Javadoc)
> @@ -62,8 +77,14 @@
>  * @see
 org.apache.ivy.core.settings.IvyVariableContainer#getVariable(
> java.lang.String)
>  */
> public String getVariable(String name) {
> -String val = (String) variables.get(name);
> -return val == null ? val : substitute(val);
> +String val = null;
> +if ((envPrefix != null) && name.startsWith(envPrefix)) {
> +val = System.getenv(name.substring(envPrefix.length()));

I think System.getenv behavior is very jre dependent. Here is the
implementation in sun JDK 1.4.2_13:
public static String getenv(String name) {
throw new Error("getenv no longer supported, use properties and -D
instead: " + name);
}

This won't really help the user :-) So maybe we could surround the call
 with
a try catch (catching Error or even Throwable, too bad they didn't use
 a
more specific throwable, we may catch OutOfMemoryError here :-( ) and
reporting the problem to the user in a more friendly way like
 "Impossible to
use Ivy environment prefix: System.getenv(String) doesn't seem to be
supported on your platform" and chaining the original Throwable.

Then in the documentation we could report that environmentPrefix is
supported only in Ant or with JRE supporting System.getenv(String)
 (i.e. >=
1.5.0 from what I know).

Xavier

-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r610562 - in /ant/ivy/core/trunk: ./ src/java/org/apache/ivy/ant/ src/java/org/apache/ivy/core/ src/java/org/apache/ivy/core/retrieve/ src/java/org/apache/ivy/core/settings/ test/java/

[Maarten Coene]

ok, shame on me. I did the test in Ant, so it was Ant that loaded the 
environment variables...
I don't have much time at the moment, but I'll see what can be done to improve 
its behaviour.

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, January 10, 2008 1:06:32 PM
Subject: Re: svn commit: r610562 - in /ant/ivy/core/trunk: ./ 
src/java/org/apache/ivy/ant/ src/java/org/apache/ivy/core/ 
src/java/org/apache/ivy/core/retrieve/ src/java/org/apache/ivy/core/settings/ 
test/java/org/apache/ivy/ant/


On Jan 10, 2008 12:43 PM, Xavier Hanin <[EMAIL PROTECTED]> wrote:

>
> On Jan 10, 2008 12:14 PM, Maarten Coene <[EMAIL PROTECTED]>
 wrote:
>
> > Strange,
> > I tested it with a sun jdk 1.4.2 (I can't check the patch level
 from
> > here) and it was working ok, so I assumed it would work for all sun
> > 1.4.2 VM's :-(
>
> Strange indeed. To be honest I haven't tested it at all, just
 navigate in
> the source from eclipse. But I assume the sources packaged with the
 jdk are
> actually the good sources. BTW since the implementation is most
 probably OS
> dependent, I should add that the source I quote is from sun jdk for
 windows.
> Maybe you ran your test on a different platform?
>
Maybe a stupid question, but did you test within an Ant build or from
 Ivy
command line?

Xavier

-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] add Nicolas Lalevée as committer

[Maarten Coene]

+1

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, February 13, 2008 10:35:49 AM
Subject: [VOTE] add Nicolas Lalevée as committer

Hi All,

Nicolas Lalevée has contributed a lot of patches to Ivy and IvyDE [1 to 10],
and has been actively involved in several discussions, especially about
IvyDE. He is always fair when giving his opinion, and often try to help
other users.

IvyDE is a subproject of Ivy considered as highly important by several users
[11], and Nicolas is greatly helping to improve it.

So I think he would make a good addition to our developer team, hence this
is a vote to make him a new committer.

Even though only votes cast by PMC members are binding [12], all votes are
welcome and important to us.

Here's my vote: +1

Xavier

[1] https://issues.apache.org/jira/browse/IVY-704
[2] https://issues.apache.org/jira/browse/IVY-702
[3] https://issues.apache.org/jira/browse/IVY-646
[4] https://issues.apache.org/jira/browse/IVYDE-62
[5] https://issues.apache.org/jira/browse/IVYDE-69
[6] https://issues.apache.org/jira/browse/IVYDE-66
[7] https://issues.apache.org/jira/browse/IVYDE-64
[8] https://issues.apache.org/jira/browse/IVYDE-76
[9] https://issues.apache.org/jira/browse/IVYDE-68
[10] https://issues.apache.org/jira/browse/IVYDE-63
[11] http://www.nabble.com/ivyde-again-td15352211.html#a15352211
[12] http://ant.apache.org/bylaws.html#Decision%20Making

-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy build broken on Java 1.4

[Maarten Coene]

This should be fixed before we release the new beta

Maarten


- Original Message 
From: Patrick Woodworth <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Tuesday, February 19, 2008 10:27:26 PM
Subject: Ivy build broken on Java 1.4

As of r629224 the Ivy build appears broken when using JDK 1.4:

compile-core:
[javac] Compiling 277 source files to E:\wstmp\ivy\build\classes\core
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:259:
cannot resolve symbol
[javac] symbol  : class Iterable
[javac] location: class
org.apache.ivy.plugins.parser.m2.PomReader.PomDependencyData
[javac] public Iterable/**/ getExcludedModules() {
[javac]^
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:176:
cannot resolve symbol
[javac] symbol  : class Iterable
[javac] location: class org.apache.ivy.plugins.parser.m2.PomReader
[javac] public Iterable/*  */ getDependencies() {
[javac]^
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:192:
cannot resolve symbol
[javac] symbol  : class Iterable
[javac] location: class org.apache.ivy.plugins.parser.m2.PomReader
[javac] public Iterable/*  */ getDependencyMgt() {
[javac]^
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:298:
cannot resolve symbol
[javac] symbol  : method getTextContent ()
[javac] location: interface org.w3c.dom.Element
[javac] return node.getTextContent();
[javac]^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 4 errors

The problem is at the API level which is why 
alone won't catch it.  You actually need to compile with a 1.4 JDK to see
the problem.





  

Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy build broken on Java 1.4

[Maarten Coene]

I've just committed a fix, it should be ok now.
Thanks for reporting.

Maarten


- Original Message 
From: Patrick Woodworth <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Tuesday, February 19, 2008 10:27:26 PM
Subject: Ivy build broken on Java 1.4

As of r629224 the Ivy build appears broken when using JDK 1.4:

compile-core:
[javac] Compiling 277 source files to E:\wstmp\ivy\build\classes\core
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:259:
cannot resolve symbol
[javac] symbol  : class Iterable
[javac] location: class
org.apache.ivy.plugins.parser.m2.PomReader.PomDependencyData
[javac] public Iterable/**/ getExcludedModules() {
[javac]^
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:176:
cannot resolve symbol
[javac] symbol  : class Iterable
[javac] location: class org.apache.ivy.plugins.parser.m2.PomReader
[javac] public Iterable/*  */ getDependencies() {
[javac]^
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:192:
cannot resolve symbol
[javac] symbol  : class Iterable
[javac] location: class org.apache.ivy.plugins.parser.m2.PomReader
[javac] public Iterable/*  */ getDependencyMgt() {
[javac]^
[javac]
E:\wstmp\ivy\src\java\org\apache\ivy\plugins\parser\m2\PomReader.java:298:
cannot resolve symbol
[javac] symbol  : method getTextContent ()
[javac] location: interface org.w3c.dom.Element
[javac] return node.getTextContent();
[javac]^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -deprecation for details.
[javac] 4 errors

The problem is at the API level which is why 
alone won't catch it.  You actually need to compile with a 1.4 JDK to see
the problem.





  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Ivy 2.0.0-beta2 Release (second attempt)

[Maarten Coene]

+1

Maarten


- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Monday, February 25, 2008 10:15:13 AM
Subject: [VOTE] Ivy 2.0.0-beta2 Release (second attempt)

I have built a second release candidate for Ivy 2.0.0-beta2.
Compared to the first attempt, the only change is that I've applied IVY-744
fix that Gilles has checked in on trunk.

You can download it from this URL:
http://people.apache.org/~xavier/ivy/staging/2.0.0-beta2/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Xavier Hanin, Ivy 2.0.0-beta2 release manager

-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cleanup Ivy DependencyResolver interface

[Maarten Coene]

Hi,

after my changes to fix IVY-716, the following methods on DependencyResolver 
are no longer used:

String[] listTokenValues(String token, Map otherTokenValues);
 OrganisationEntry[] listOrganisations();
ModuleEntry[] listModules(OrganisationEntry org);
RevisionEntry[] listRevisions(ModuleEntry module);

Shall I start removing these methods (and all related code), or will we keep 
them (maybe deprecated) to avoid breaking external code that is using the 
DependencyResolver interface directly?

Maarten




  

OMG, Sweet deal for Yahoo! users/friends:Get A Month of Blockbuster Total 
Access, No Cost. W00t 
http://tc.deals.yahoo.com/tc/blockbuster/text2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy settings id (was Re: Merge 641903 from trunk to 1.7 branch?)

[Maarten Coene]

Can't we just deprecate the "id" attribute on the settings task and use the 
settingsId attribute instead?



instead of 



Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Friday, March 28, 2008 4:31:42 PM
Subject: Ivy settings id (was Re: Merge 641903 from trunk to 1.7 branch?)

On Fri, Mar 28, 2008 at 4:08 PM, Dominique Devienne <[EMAIL PROTECTED]>
wrote:

> On Fri, Mar 28, 2008 at 8:00 AM, Xavier Hanin <[EMAIL PROTECTED]>
> wrote:
> > On Fri, Mar 28, 2008 at 1:23 PM, Gilles Scokart <[EMAIL PROTECTED]>
> wrote:
> >  > +1 for me as well (let's put a little bit more presure from the Ivy
> guys ;-).
> >  >
> >  > To come back to the impact on Ivy, I think we should put a note in
> our
> >  > doc saying that using the settings task with an id requires 1.7.1.
> >
> >  We can put a reference to the bug, the problem occurs only when you
> call ant
> >  with multiple targets, each depending on the same settings, so I think
> >  people can use Ivy settings with with ant 1.7.0 without running into
> the
> >  problem.
>
> For the record, I think it's bad Ant style to use ids in tasks. This
> is kept around for BC, but should be discouraged. Using ids on types
> OTOH is OK, and essential to types in fact. If a task should refer to
> part of another task's internal config, this hints to the config
> needing to be its own type referred to by both tasks. It's even OK for
> the type to be implicitly created by the first task, when it receives
> for example a configid="foo" attribute, so that the second task can
> use it using configrefid="foo" or a nested .
>
> I'm not sure how Ivy does it exactly, but somehow I got the feel from
> the discussions that it's using the "deprecated" id'd task pattern,
> which is a "bad" pattern IMHO. Hopefully I got the wrong feeling ;-)

I think we use that bad pattern. We've been wondering about the best form
settings should take for a while. It used to be a datatype in 2.0 alpha, but
we were running into trouble because a datatype has no lifecycle. Hence in a
discussion  Peter suggested to make it a task, using the id as we did before
for the datatype but with a default value:
http://markmail.org/message/52hqry734myzopts

This works pretty well from a user point of view who don't really know if
it's a task or datatype and don't really care. Except that we run into this
bug, and this bad pattern. So, what would you suggest? Is there something we
could do better while still preserving the behaviour we have now?

Xavier

>
>
> --DD
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Like movies? Here's a limited-time offer: Blockbuster Total Access for one 
month at no cost. 
http://tc.deals.yahoo.com/tc/blockbuster/text4.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy settings id (was Re: Merge 641903 from trunk to 1.7 branch?)

[Maarten Coene]

I don't think the tasks should be stateless, I think it's fine the way it is 
now.
There are other examples of tasks that must be executed one ofther the other, 
like:
setProxy -> must be executed before outgoing http connections are made if you 
have a proxy
the Clover tasks -> the setup task must be executed first
junitreport -> is sharing state with the junit tasks through xml files, a bit 
the same as the postresolve task can share state with the resolve task by 
parsing the XML resolve report.

If we keep ivy:settings to be a task, we should do 2 things:
- rename the "id" attribute to something else
- rename "ivy:settings" to something else to make it more clear what it does to 
avoid confusion. But I think Gilles has a point here about the ivy:configure 
task. I don't see a difference between the "ivy:settings" task and the 
"ivy:configure" task, except the ability to specify a settings id.

So, I think we should do the following:
1. undeprecate the "ivy:configure" task and add a settingsId attribute to it 
(and the other settings attributes that aren't present on ivy:configure)
2. undefine the "ivy:settings" task (just remove it from the antlib.xml)
3. refactor the IvyAntSettingsTask (or whatever it's name is) to be a real 
datatype, which will be created internally by ivy:configure and used in all the 
other Ivy tasks. But don't make this datatype available for usage in the ant 
scripts yet. This way, it will be easy to support the use-case of lazy-loading 
the Ivy settings once we think it's usefull to support it.

Maarten


- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Sunday, March 30, 2008 5:52:39 PM
Subject: Re: Ivy settings id (was Re: Merge 641903 from trunk to 1.7 branch?)

On Sat, Mar 29, 2008 at 7:23 PM, Gilles Scokart <[EMAIL PROTECTED]> wrote:

> I'm -1 to rename ivy:settings into ivy:loadsettings.  If you realy
> want something like that, then it would be better to go back to the
> ivy:configure (and I would be -0.5).
>
> The reason I think ivy:settings should be a data-type (or look like a
> data type) is because every ant task are "standalone".  I don't know
> any example of 2 tasks that should be executed one after the other,
> while it is usual to have an ant task depending on a pre-declared
> datatype.

First, if we really want to have all Ivy tasks stateless, we should change
resolve too. The problem is exactly the same between resolve and any post
resolve task as it is between settings and any other task.
Second, I see an example of tasks somewhat depending on one another: taskdef
and any task declared by the taskdef.
So I think loading settings with a task is consistent with resolving
dependencies with a task, and I think it's the only way we have to actually
load the settings when the user wants. If datatype were not lazily
initialized I think I'd be in favour of using a datatype. But with the
current facts I'm not.

Xavier


>
> An other way to say that is that every tasks are "stateless".  The
> only exceptions is the properties task, which for me look like a data
> declaration.


>
> That's why Ant is a declarative langage, and not a procedural langage.
>  I consider ivy:configure "command" as a procedural command and not a
> declarative one.
>
> Now, I agree that the declarative aproach leas to some issues.  One of
> them is that the datatype are curently always processed lazily (the
> first time they are used) and thus the errors are also reported
> lazily, which make the debuging more complex.
>
> Anyway, even if I like the suggestion of Dominique (the user that
> don't want to put a settingsRef should use ivy:configure in BC mode),
> it has a drawback.  If the user forget to put its settingsRef, he will
> not receive any error message, the code will run with the default
> settings, even if an other settings is defined.  This lead to problem
> difficult to debug.
>
> Gilles
>
>
> On 29/03/2008, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> > On Fri, Mar 28, 2008 at 11:50 PM, Dominique Devienne <
> [EMAIL PROTECTED]>
> >  wrote:
> >
> >
> >  > On Fri, Mar 28, 2008 at 5:40 PM, Maarten Coene <
> [EMAIL PROTECTED]>
> >  > wrote:
> >  > > Can't we just deprecate the "id" attribute on the settings task and
> use
> >  > the settingsId attribute instead?
> >  >
> >  > id is handled by Ant itself, in the core. I don't think you can
> deprecate
> >  > it.
> >
> >
> > I think we would deprecate the usage we do of id, not really the
> attribute
> >  itself. And I don't think we even 

Re: Fixing some naming inconsistencies in Ivy

[Maarten Coene]

I like the enumeration syntax, like descriptor="required | otpional", it's much 
more readable and it will probably allow us to have less attributes on some of 
the tasks.

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Saturday, March 29, 2008 10:09:23 AM
Subject: Re: Fixing some naming inconsistencies in Ivy

Just pinging about this e-mail, I've had no answer so far, I think I can't
make the choice alone, and we need to deal with that question before
2.0final to close IVY-297. So, anyone has an opinion about this:

On Fri, Feb 29, 2008 at 12:31 PM, Xavier Hanin <[EMAIL PROTECTED]>
wrote:

> Hi,
>
> As reported by IVY-297, Ivy suffers from some name inconsistencies and
> strange attribute names. Ivy 2.0 is a good opportunity to fix some of
> them, since I think we can afford some more deprecation warnings.
>
> So I'd like to fix IVY-297 by marking allownomd as deprecated, and
> providing a descriptor="required | optional" attribute.
>
> To go further, we could rename the attribute skipbuildwithoutivy in
> buildlist in skipbuildwithoutdescriptor, or even better change it to
> buildwithoutdescriptor="skip | fail | warn | tail | head", which wold make
> it both more readable and more powerful.
>
> Another area where the name 'ivy' is used to talk about module descriptors
> in general is patterns. This lead to some strange settings, where you give
> an 'ivy' pattern to tell where the poms are. In this case I think we could
> support both 'ivy' and 'descriptor' (for resolver patterns for instance),
> since the use case for ivy files is still predominant, so I don't think
> deprecating the old name would really be better.
>
> So, what do you think about these changes?
>
> Xavier
>
>
-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt doc/resolver/ssh.html src/java/org/apache/ivy/plugins/repository/ssh/Scp.java src/java/org/apache/ivy/plugins/repository/ssh/SshRepository

[Maarten Coene]

It was hardcoded to 0600 in Scp.java before I made this change. To keep it BC, 
I defaulted it to the same value. As far as I could see, the umask wasn't used. 
Since this attribute is only used for publishing modules, not for module 
retrieval, I think we should at least keep "publish" in the attribute name, but 
renaming 'mode' to 'permissions' (or something else) is fine for me.

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Friday, April 4, 2008 8:51:18 AM
Subject: Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt 
doc/resolver/ssh.html src/java/org/apache/ivy/plugins/repository/ssh/Scp.java 
src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java

On Fri, Apr 4, 2008 at 12:49 AM, <[EMAIL PROTECTED]> wrote:

> Author: maartenc
> Date: Thu Apr  3 15:49:49 2008
> New Revision: 644541
>
> URL: http://svn.apache.org/viewvc?rev=644541&view=rev
> Log:
> IMPROVEMENT: make it possible to specify permissions of published files
> for the SSH resolver (IVY-764) + removal of some unused code
>
> Modified:
>ant/ivy/core/trunk/CHANGES.txt
>ant/ivy/core/trunk/doc/resolver/ssh.html
>
>  ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
>
>  
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java
>
> Modified: ant/ivy/core/trunk/CHANGES.txt
> URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/CHANGES.txt?rev=644541&r1=644540&r2=644541&view=diff
>
> ==
> --- ant/ivy/core/trunk/CHANGES.txt (original)
> +++ ant/ivy/core/trunk/CHANGES.txt Thu Apr  3 15:49:49 2008
> @@ -69,6 +69,7 @@
>  - NEW: Add a new resolve mode (optionally per module) to utilize dynamic
> constraint rule metadata (IVY-740)
>  - NEW: Add transitive dependency version and branch override mechanism
> (IVY-784)
>
> +- IMPROVEMENT: make it possible to specify permissions of published files
> for the SSH resolver (IVY-764)
>  - IMPROVEMENT: Load Ivy version number into some Ant property (IVY-790)
>  - IMPROVEMENT: Make Ivy standalone runnable with no required dependencies
> (IVY-757)
>  - IMPROVEMENT: add branch attribute in ivy:install task (IVY-727)
>
> Modified: ant/ivy/core/trunk/doc/resolver/ssh.html
> URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/resolver/ssh.html?rev=644541&r1=644540&r2=644541&view=diff
>
> ==
> --- ant/ivy/core/trunk/doc/resolver/ssh.html (original)
> +++ ant/ivy/core/trunk/doc/resolver/ssh.html Thu Apr  3 15:49:49 2008
> @@ -56,6 +56,8 @@
> No, defaults to host given on the patterns, fail if none is
> set
> portThe port to connect to
> No, defaults to 22
> +publishModeA four digit string (e.g., 0644, see "man
> chmod", "man open") specifying the permissions of the published files.  class="since">(since 2.0)
> +No, defaults to 0600

Is it a good idea to give a default value to this attribute? This will break
BC, it used to be using the umask, right? I wonder if the default shouldn't
be "use the umask" to preserve BC. WDYT?

BTW, I don't like the name "publishMode". What do you think of "permissions"
or "umask"?

Xavier



>
>  
>  
>  Child elements
>
> Modified:
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java?rev=644541&r1=644540&r2=644541&view=diff
>
> ==
> ---
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> (original)
> +++
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> Thu Apr  3 15:49:49 2008
> @@ -276,41 +276,6 @@
> fileInfo.setLastModified(modtime);
> }
>
> -private void sendBytes(Channel channel, byte[] data, String fileName,
> String mode)
> -throws IOException, RemoteScpException {
> -OutputStream os = channel.getOutputStream();
> -InputStream is = new BufferedInputStream(
> -channel.getInputStream(), SEND_BYTES_BUFFER_LENGTH);
> -
> -try {
> -if (channel.isConnected()) {
> -channel.start();
> -} else {
> -channel.connect();
> -}
> -} catch (JSchException e1) {
> -throw (IOException) new IOException("Channel connection
> problems").initCause(e1);
> -}
> -
> -readResponse(is);
> -
> -String cline = "C" + mode + " " + data.length + " " + fileName +
> "\n";
> -
> -os.write(cline.getBytes());
> -os.flush();
> -
> -readResponse(is);
> -
> -os.write(data, 0, data.length);
> -os.write(0);
> -os.flush();
> -
> -readResponse(is);
> -
> -os.write("E\n".getBytes());
> -os.flush();
> 

Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt doc/resolver/ssh.html src/java/org/apache/ivy/plugins/repository/ssh/Scp.java src/java/org/apache/ivy/plugins/repository/ssh/SshRepository

[Maarten Coene]

Btw, in the manual for chmod, they use the "mode" terminology for this kind of 
information.

Maarten

- Original Message ----
From: Maarten Coene <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Friday, April 4, 2008 9:19:57 AM
Subject: Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt 
doc/resolver/ssh.html src/java/org/apache/ivy/plugins/repository/ssh/Scp.java 
src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java

It was hardcoded to 0600 in Scp.java before I made this change. To keep it BC, 
I defaulted it to the same value. As far as I could see, the umask wasn't used. 
Since this attribute is only used for publishing modules, not for module 
retrieval, I think we should at least keep "publish" in the attribute name, but 
renaming 'mode' to 'permissions' (or something else) is fine for me.

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Friday, April 4, 2008 8:51:18 AM
Subject: Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt 
doc/resolver/ssh.html src/java/org/apache/ivy/plugins/repository/ssh/Scp.java 
src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java

On Fri, Apr 4, 2008 at 12:49 AM, <[EMAIL PROTECTED]> wrote:

> Author: maartenc
> Date: Thu Apr  3 15:49:49 2008
> New Revision: 644541
>
> URL: http://svn.apache.org/viewvc?rev=644541&view=rev
> Log:
> IMPROVEMENT: make it possible to specify permissions of published files
> for the SSH resolver (IVY-764) + removal of some unused code
>
> Modified:
>ant/ivy/core/trunk/CHANGES.txt
>ant/ivy/core/trunk/doc/resolver/ssh.html
>
>  ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
>
>  
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java
>
> Modified: ant/ivy/core/trunk/CHANGES.txt
> URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/CHANGES.txt?rev=644541&r1=644540&r2=644541&view=diff
>
> ==
> --- ant/ivy/core/trunk/CHANGES.txt (original)
> +++ ant/ivy/core/trunk/CHANGES.txt Thu Apr  3 15:49:49 2008
> @@ -69,6 +69,7 @@
>  - NEW: Add a new resolve mode (optionally per module) to utilize dynamic
> constraint rule metadata (IVY-740)
>  - NEW: Add transitive dependency version and branch override mechanism
> (IVY-784)
>
> +- IMPROVEMENT: make it possible to specify permissions of published files
> for the SSH resolver (IVY-764)
>  - IMPROVEMENT: Load Ivy version number into some Ant property (IVY-790)
>  - IMPROVEMENT: Make Ivy standalone runnable with no required dependencies
> (IVY-757)
>  - IMPROVEMENT: add branch attribute in ivy:install task (IVY-727)
>
> Modified: ant/ivy/core/trunk/doc/resolver/ssh.html
> URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/resolver/ssh.html?rev=644541&r1=644540&r2=644541&view=diff
>
> ==
> --- ant/ivy/core/trunk/doc/resolver/ssh.html (original)
> +++ ant/ivy/core/trunk/doc/resolver/ssh.html Thu Apr  3 15:49:49 2008
> @@ -56,6 +56,8 @@
> No, defaults to host given on the patterns, fail if none is
> set
> portThe port to connect to
> No, defaults to 22
> +publishModeA four digit string (e.g., 0644, see "man
> chmod", "man open") specifying the permissions of the published files.  class="since">(since 2.0)
> +No, defaults to 0600

Is it a good idea to give a default value to this attribute? This will break
BC, it used to be using the umask, right? I wonder if the default shouldn't
be "use the umask" to preserve BC. WDYT?

BTW, I don't like the name "publishMode". What do you think of "permissions"
or "umask"?

Xavier



>
>  
>  
>  Child elements
>
> Modified:
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java?rev=644541&r1=644540&r2=644541&view=diff
>
> ==
> ---
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> (original)
> +++
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> Thu Apr  3 15:49:49 2008
> @@ -276,41 +276,6 @@
> fileInfo.setLastModified(modtime);
> }
>
> -private void sendBytes(Channel channel, byte[] data, String fileName,
> String mode)
> -throws IOException, RemoteScpException {
> -OutputStream os = channel.getOutputS

Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt doc/resolver/ssh.html src/java/org/apache/ivy/plugins/repository/ssh/Scp.java src/java/org/apache/ivy/plugins/repository/ssh/SshRepository

[Maarten Coene]

publishPermissions is fine for me, we can use the "chmod mode" terminology in 
the documentation of this attribute.

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Friday, April 4, 2008 9:45:57 AM
Subject: Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt 
doc/resolver/ssh.html src/java/org/apache/ivy/plugins/repository/ssh/Scp.java 
src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java

On Fri, Apr 4, 2008 at 9:24 AM, Maarten Coene <[EMAIL PROTECTED]>
wrote:

> Btw, in the manual for chmod, they use the "mode" terminology for this
> kind of information.

Maybe it's only me then, but I think mode is too generic in this situation.
Moreover we have resolveMode option on the resolve task (introduced
recently), and I think we could later end up with the same kind of need on
publish, in which case we couldn't use publishMode to avoid the confusion if
we keep it for this attribute. What do you think?

Xavier


>
>
> Maarten
>
> - Original Message 
> From: Maarten Coene <[EMAIL PROTECTED]>
> To: Ant Developers List 
> Sent: Friday, April 4, 2008 9:19:57 AM
> Subject: Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt
> doc/resolver/ssh.html
> src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java
>
> It was hardcoded to 0600 in Scp.java before I made this change. To keep it
> BC, I defaulted it to the same value. As far as I could see, the umask
> wasn't used. Since this attribute is only used for publishing modules, not
> for module retrieval, I think we should at least keep "publish" in the
> attribute name, but renaming 'mode' to 'permissions' (or something else) is
> fine for me.
>
> Maarten
>
> - Original Message 
> From: Xavier Hanin <[EMAIL PROTECTED]>
> To: dev@ant.apache.org
> Sent: Friday, April 4, 2008 8:51:18 AM
> Subject: Re: svn commit: r644541 - in /ant/ivy/core/trunk: CHANGES.txt
> doc/resolver/ssh.html
> src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java
>
> On Fri, Apr 4, 2008 at 12:49 AM, <[EMAIL PROTECTED]> wrote:
>
> > Author: maartenc
> > Date: Thu Apr  3 15:49:49 2008
> > New Revision: 644541
> >
> > URL: http://svn.apache.org/viewvc?rev=644541&view=rev
> > Log:
> > IMPROVEMENT: make it possible to specify permissions of published files
> > for the SSH resolver (IVY-764) + removal of some unused code
> >
> > Modified:
> >ant/ivy/core/trunk/CHANGES.txt
> >ant/ivy/core/trunk/doc/resolver/ssh.html
> >
> >
>  ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/Scp.java
> >
> >
>  
> ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/repository/ssh/SshRepository.java
> >
> > Modified: ant/ivy/core/trunk/CHANGES.txt
> > URL:
> >
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/CHANGES.txt?rev=644541&r1=644540&r2=644541&view=diff
> >
> >
> ==
> > --- ant/ivy/core/trunk/CHANGES.txt (original)
> > +++ ant/ivy/core/trunk/CHANGES.txt Thu Apr  3 15:49:49 2008
> > @@ -69,6 +69,7 @@
> >  - NEW: Add a new resolve mode (optionally per module) to utilize
> dynamic
> > constraint rule metadata (IVY-740)
> >  - NEW: Add transitive dependency version and branch override mechanism
> > (IVY-784)
> >
> > +- IMPROVEMENT: make it possible to specify permissions of published
> files
> > for the SSH resolver (IVY-764)
> >  - IMPROVEMENT: Load Ivy version number into some Ant property (IVY-790)
> >  - IMPROVEMENT: Make Ivy standalone runnable with no required
> dependencies
> > (IVY-757)
> >  - IMPROVEMENT: add branch attribute in ivy:install task (IVY-727)
> >
> > Modified: ant/ivy/core/trunk/doc/resolver/ssh.html
> > URL:
> >
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/resolver/ssh.html?rev=644541&r1=644540&r2=644541&view=diff
> >
> >
> ==
> > --- ant/ivy/core/trunk/doc/resolver/ssh.html (original)
> > +++ ant/ivy/core/trunk/doc/resolver/ssh.html Thu Apr  3 15:49:49 2008
> > @@ -56,6 +56,8 @@
> > No, defaults to host given on the patterns, fail if none is
> > set
> > portThe port to connect to
> > No, defaults to 22
> > +publishModeA four digit string (e.g., 0644, see
> "man
> > chmod", "

Re: [VOTE] migrate Ivy's wiki to Confluence

[Maarten Coene]

Are we going to use confluence as a replacement for our current website 
(http://ant.apache.org/ivy), or only as a replacement for our wiki 
(http://wiki.apache.org/ivy/) ?

Maarten


- Original Message 
From: Paul King <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, April 23, 2008 4:36:07 PM
Subject: Re: [VOTE] migrate Ivy's wiki to Confluence


If you can move straight in to Confluence 2.8, that will let you
do page ordering which helps a lot if you want to export your
site to PDF as a User Guide/PDF manual. It also seems to do
a slightly better job formatting code examples.

Cheers, Paul.

Archie Cobbs wrote:
> Not sure if my vote counts, but +1 from me in any case :-)
> 
> -Archie
> 
> On Wed, Apr 23, 2008 at 2:41 AM, Xavier Hanin <[EMAIL PROTECTED]>
> wrote:
> 
>> Hi,
>>
>> There's been a discussion recently about Ivy's documentation, which end up
>> discussing user contributed documentation and especially the wiki.
>>
>> It seems 2 Ivy committers would prefer to use Confluence for Ivy wiki:
>> http://markmail.org/message/n4mvsmowb3ujlyeg
>>
>> Moreover, some users expressed their opinion about this preference too:
>> http://markmail.org/message/kjbzcqukzhqrowwt
>>
>> I already expressed the reasons why I'd like to migrate:
>> "First, in JIRA we have activated the wiki syntax, which is the same as
>> confluence one. So using confluence it would be only one wiki syntax to
>> learn for both the wiki and issues. Secondly, I think with confluence you
>> have a rich text editor, which can be useful for people who don't want to
>> learn the syntax, or for tables which are cumbersome to write and maintain
>> in wiki syntax. Lastly, I much prefer the look of confluence pages over *
>> MoinMoin*."
>>
>> So I'd like to start a vote to see if migrating Ivy's wiki to confluence
>> is
>> possible.
>>
>> Xavier
>> --
>> Xavier Hanin - Independent Java Consultant
>> http://xhab.blogspot.com/
>> http://ant.apache.org/ivy/
>> http://www.xoocode.org/
>>
> 
> 
> 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] migrate Ivy's wiki to Confluence

[Maarten Coene]

ok, in that case +1 for me

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, April 23, 2008 6:13:56 PM
Subject: Re: [VOTE] migrate Ivy's wiki to Confluence

On Wed, Apr 23, 2008 at 5:18 PM, Nicolas Lalevée <[EMAIL PROTECTED]>
wrote:

> Le mercredi 23 avril 2008, Maarten Coene a écrit :
> > Are we going to use confluence as a replacement for our current website
> > (http://ant.apache.org/ivy), or only as a replacement for our wiki
> > (http://wiki.apache.org/ivy/) ?
>
> The vote is only for the wiki. We didn't discussed about changing the way
> we
> are editing the website. For me the website is cool as it is.

Same for me.

Xavier


>
>
> Nicolas
>
>
> >
> > Maarten
> >
> >
> > - Original Message 
> > From: Paul King <[EMAIL PROTECTED]>
> > To: Ant Developers List 
> > Sent: Wednesday, April 23, 2008 4:36:07 PM
> > Subject: Re: [VOTE] migrate Ivy's wiki to Confluence
> >
> >
> > If you can move straight in to Confluence 2.8, that will let you
> > do page ordering which helps a lot if you want to export your
> > site to PDF as a User Guide/PDF manual. It also seems to do
> > a slightly better job formatting code examples.
> >
> > Cheers, Paul.
> >
> > Archie Cobbs wrote:
> > > Not sure if my vote counts, but +1 from me in any case :-)
> > >
> > > -Archie
> > >
> > > On Wed, Apr 23, 2008 at 2:41 AM, Xavier Hanin <[EMAIL PROTECTED]>
> > >
> > > wrote:
> > >> Hi,
> > >>
> > >> There's been a discussion recently about Ivy's documentation, which
> end
> > >> up discussing user contributed documentation and especially the wiki.
> > >>
> > >> It seems 2 Ivy committers would prefer to use Confluence for Ivy
> wiki:
> > >> http://markmail.org/message/n4mvsmowb3ujlyeg
> > >>
> > >> Moreover, some users expressed their opinion about this preference
> too:
> > >> http://markmail.org/message/kjbzcqukzhqrowwt
> > >>
> > >> I already expressed the reasons why I'd like to migrate:
> > >> "First, in JIRA we have activated the wiki syntax, which is the same
> as
> > >> confluence one. So using confluence it would be only one wiki syntax
> to
> > >> learn for both the wiki and issues. Secondly, I think with confluence
> > >> you have a rich text editor, which can be useful for people who don't
> > >> want to learn the syntax, or for tables which are cumbersome to write
> > >> and maintain in wiki syntax. Lastly, I much prefer the look of
> > >> confluence pages over * MoinMoin*."
> > >>
> > >> So I'd like to start a vote to see if migrating Ivy's wiki to
> confluence
> > >> is
> > >> possible.
> > >>
> > >> Xavier
> > >> --
> > >> Xavier Hanin - Independent Java Consultant
> > >> http://xhab.blogspot.com/
> > >> http://ant.apache.org/ivy/
> > >> http://www.xoocode.org/
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> >
> >
> >
> ___
> >_ Be a better friend, newshound, and
> > know-it-all with Yahoo! Mobile.  Try it now.
> > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Releasing IvyDE

[Maarten Coene]

+1 for an IvyDE release.
I'd prefer a beta release instead of an alpha release though...

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Monday, May 19, 2008 6:19:40 PM
Subject: Re: Releasing IvyDE

On Mon, May 19, 2008 at 4:49 PM, Nicolas Lalevée <[EMAIL PROTECTED]>
wrote:

> Hi,
>
> Recently there were some users complaining that there is no release of
> IvyDE
> compatible with Ivy 2. [1] [2]
>
> I know that IvyDE is not stable. See some major issues in Jira. For some
> people it is even getting less stable: [3]
>
> But then I wonder if we could still do an alpha release, just to get people
> less annoyed by the 1.2 version which has some terrible issues [2], and
> probably more bug report, and hopefully more people interested in
> contributing.
>
> WDYT ?

I'm  a strong +1 to get an alpha release of IvyDE out. I don't have much
time currently though, but according to the high quality of the job you've
done so far on IvyDE and its build system, I'm confident you are able to be
the release manager for this version if you want.

Xavier


>
>
> Nicolas
>
> [1]
>
> http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200805.mbox/[EMAIL 
> PROTECTED]
> [2] https://issues.apache.org/jira/browse/IVYDE-65
> [3]
>
> http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200805.mbox/[EMAIL 
> PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Ivy] How to add a new option to ivy settings

[Maarten Coene]

Why not always use the server timestamp for the artifacts as we already do for 
the Ivy files?

Maarten

- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, May 29, 2008 8:51:36 AM
Subject: Re: [Ivy] How to add a new option to ivy settings

As Gilles suggested, I'd better put that in settings, which is also much
easier to add (you only need a setter on the resolver to recognize an
attribute for the resolver in the settings file, pretty much like how Ant
tasks work). Still to do what you want in the ivy file you have to modify
XmlModuleDescriptorParser, the ModuleDescriptor interface and its default
implementation.

HTH,

Xavier

On Thu, May 29, 2008 at 6:13 AM, Claudio Miranda <[EMAIL PROTECTED]>
wrote:

>
>
>I modified the code displayed below.
>At BasicURLHandler, how is it possible to retrieve de value of
> "timestamp" attribute  (from ivy.xml)
>
> Index: src/java/org/apache/ivy/util/url/BasicURLHandler.java
> ===
> --- src/java/org/apache/ivy/util/url/BasicURLHandler.java   (revision
> 661197)
> +++ src/java/org/apache/ivy/util/url/BasicURLHandler.java   (working
> copy)
> @@ -131,6 +131,10 @@
> "Downloaded file size doesn't match expected
> Content Length for " + src
> + ". Please retry.");
> }
> +boolean remoteTimestamp = false;
> +if (remoteTimestamp) {
> +dest.setLastModified(srcConn.getLastModified());
> +}
> } finally {
> disconnect(srcConn);
>
>
> Index: src/java/org/apache/ivy/plugins/parser/xml/ivy.xsd
> ===
> --- src/java/org/apache/ivy/plugins/parser/xml/ivy.xsd  (revision 661197)
> +++ src/java/org/apache/ivy/plugins/parser/xml/ivy.xsd  (working copy)
> @@ -229,10 +229,19 @@
>
>
>
> -name="defaultconf" type="xs:string"/>
> -name="defaultconfmapping" type="xs:string"/>
> + type="xs:string"/>
> + type="xs:string"/>
>  type="xs:boolean" />
> - 
> + use="optional">
> + 
> +
> +
> +
> +
> +
> +
> +
>
>
>
> Index:
> src/java/org/apache/ivy/plugins/parser/xml/XmlModuleDescriptorParser.java
> ===
> ---
> src/java/org/apache/ivy/plugins/parser/xml/XmlModuleDescriptorParser.java
> (revision 661197)
> +++
> src/java/org/apache/ivy/plugins/parser/xml/XmlModuleDescriptorParser.java
> (working copy)
> @@ -520,6 +520,10 @@
> if (confMappingOverride != null) {
>
> md.setMappingOverride(Boolean.valueOf(confMappingOverride).booleanValue());
> }
> +String timestamp =
> ivy.substitute(attributes.getValue("timestamp"));
> +if (timestamp != null) {
> +md.setTimestamp(timestamp);
> +}
> checkConfigurations();
>
>
> Claudio Miranda wrote:
> >
> >
> > I am doing some testing with Ivy and have implemented a small
> > modification, to allow the downloaded resource to have the same date
> > timestamp as the file in remote repo. It is a requirement from the
> > customer.
> >
> > At org.apache.ivy.util.url.BasicURLHandler.download(URL src, File
> > dest, CopyProgressListener l)
> > I added
> >
> > dest.setLastModified(srcConn.getLastModified());
> >
> > How is it possible to add an attribute "timestamp" to the
> > "dependencies" xml tag ? See below, a sample:
> >
> > 
> > 
> > 
> >   
> >   
> >   
> > 
> > 
> >
> > It can have 2 values "remote" or "current", whereas "remote" set the
> > last modified attribute, as the remote file is. The "current" means the
> > current Ivy behavior.
> >
> > How can I read the timestamp value, at BasicURLHandler class ?
> >
> > This is the thread, with more explanation about this requested
> > behavior
> >
> http://www.nabble.com/How-to-download-files-from-ivyrepo-with-the-same-last-modified-date---td17515745.html
> >
> > I plan to submit it as an enhancement to the Ivy issue tracking.
> >
> > Thanks
> >
> > Claudio Miranda
> >
>
>
> -
> Claudio Miranda
> http://weblogs.java.net/blog/claudio
> http://www.claudius.com.br/blog
> --
> View this message in context:
> http://www.nabble.com/-Ivy--How-to-add-a-new-option-to-ivy-settings-tp17526130p17527290.html
> Sent from the Ant - Dev mail

Re: [Ivy] How to add a new option to ivy settings

[Maarten Coene]

So maybe it should be an attribute on the ivy:retrieve task?
I think the files in the cache should have the same timestamp as on the server.
This way, you still have the choice what you want to do with the timestamp when 
the artifacts are already resolved.

Maarten


- Original Message 
From: Gilles Scokart <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, May 29, 2008 9:51:58 AM
Subject: Re: [Ivy] How to add a new option to ivy settings

Maybe because later an other user will have the oposite requirements :
I want the retreive to use the current timestamp, so that I know when
I made the retrieve, I know which files have been updated by my last
retrieve, I can use some kind of up-to-date task, and I can also
better integrate my retrieved libraries into my source control
repository.

I think both requirements are valid, so it should be configurable.

Gilles

2008/5/29 Xavier Hanin <[EMAIL PROTECTED]>:
> On Thu, May 29, 2008 at 9:35 AM, Maarten Coene <[EMAIL PROTECTED]>
> wrote:
>
>> Why not always use the server timestamp for the artifacts as we already do
>> for the Ivy files?
>
> Why not, indeed, I see no specific reason.
>
> Xavier
>
>
>>
>>
>> Maarten
>>
>> - Original Message 
>> From: Xavier Hanin <[EMAIL PROTECTED]>
>> To: Ant Developers List 
>> Sent: Thursday, May 29, 2008 8:51:36 AM
>> Subject: Re: [Ivy] How to add a new option to ivy settings
>>
>> As Gilles suggested, I'd better put that in settings, which is also much
>> easier to add (you only need a setter on the resolver to recognize an
>> attribute for the resolver in the settings file, pretty much like how Ant
>> tasks work). Still to do what you want in the ivy file you have to modify
>> XmlModuleDescriptorParser, the ModuleDescriptor interface and its default
>> implementation.
>>
>> HTH,
>>
>> Xavier
>>
>> On Thu, May 29, 2008 at 6:13 AM, Claudio Miranda <[EMAIL PROTECTED]>
>> wrote:
>>
>> >
>> >
>> >I modified the code displayed below.
>> >At BasicURLHandler, how is it possible to retrieve de value of
>> > "timestamp" attribute  (from ivy.xml)
>> >
>> > Index: src/java/org/apache/ivy/util/url/BasicURLHandler.java
>> > ===
>> > --- src/java/org/apache/ivy/util/url/BasicURLHandler.java   (revision
>> > 661197)
>> > +++ src/java/org/apache/ivy/util/url/BasicURLHandler.java   (working
>> > copy)
>> > @@ -131,6 +131,10 @@
>> > "Downloaded file size doesn't match expected
>> > Content Length for " + src
>> > + ". Please retry.");
>> > }
>> > +boolean remoteTimestamp = false;
>> > +if (remoteTimestamp) {
>> > +dest.setLastModified(srcConn.getLastModified());
>> > +}
>> > } finally {
>> > disconnect(srcConn);
>> >
>> >
>> > Index: src/java/org/apache/ivy/plugins/parser/xml/ivy.xsd
>> > ===
>> > --- src/java/org/apache/ivy/plugins/parser/xml/ivy.xsd  (revision 661197)
>> > +++ src/java/org/apache/ivy/plugins/parser/xml/ivy.xsd  (working copy)
>> > @@ -229,10 +229,19 @@
>> >
>> >
>> >
>> > -   > > name="defaultconf" type="xs:string"/>
>> > -   > > name="defaultconfmapping" type="xs:string"/>
>> > +> > type="xs:string"/>
>> > +> > type="xs:string"/>
>> > > > type="xs:boolean" />
>> > - 
>> > +> > use="optional">
>> > + 
>> > +
>> > +
>> > +
>> > +
>> > +
>> > +
>> > +
>> >
>> >
>> >
>> > Index:
>> > src/java/org/apache/ivy/plugins/parse

Re: [Ivy] How to add a new option to ivy settings

[Maarten Coene]

I suggest you do the following:

1. create a JIRA issue for this
2. modify BasicURLHandler.java to always set the modification date on the 
downloaded file
3. check if this change has the effect you wanted
4. if test results are ok, attach a patch to your JIRA issue for 
BasicURLHandler.java


Maarten



- Original Message 
From: Claudio Miranda <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Thursday, May 29, 2008 1:31:16 PM
Subject: Re: [Ivy] How to add a new option to ivy settings



Hey guys, thank you for your suggestions.

I started to better understand Ivy 2 days ago, and I have no knowledge
about how to read those configurations.

Can you show me some code or guidance on how to better acomplish this
task ?
I have already modified XmlModuleDescriptorParser and ModuleDescriptor
implementation (I will do the same to the interface).

Thanks

Claudio Miranda


Xavier Hanin wrote:
> 
> As Gilles suggested, I'd better put that in settings, which is also much
> easier to add (you only need a setter on the resolver to recognize an
> attribute for the resolver in the settings file, pretty much like how Ant
> tasks work). Still to do what you want in the ivy file you have to modify
> XmlModuleDescriptorParser, the ModuleDescriptor interface and its default
> implementation.
> 


-
Claudio Miranda
http://weblogs.java.net/blog/claudio
http://www.claudius.com.br/blog
-- 
View this message in context: 
http://www.nabble.com/-Ivy--How-to-add-a-new-option-to-ivy-settings-tp17526130p17533140.html
Sent from the Ant - Dev mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Release of Apache IvyDE 2.0.0.alpha1 (take 2)

[Maarten Coene]

I've installed it using the update site on my Eclipse 3.4 without a problem.
I've only used it for some very basic things and I didn't had any problem so 
far

So, here is my +1

Maarten


- Original Message 
From: Nicolas Lalevée <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Sunday, June 22, 2008 11:23:12 PM
Subject: [VOTE] Release of Apache IvyDE 2.0.0.alpha1 (take 2)

Here the second try to release IvyDE.

You can now found the new build here:
http://people.apache.org/~hibou/ivyde-2.0.0.alpha1/
You can test the updatesite in Eclipse with that URL:
http://people.apache.org/~hibou/ivyde-2.0.0.alpha1/updatesite

In this build, I have fixed two issues.
* the sources were missing a file which makes the build fail
* the binaries of Ivy where not available in the binary package  
org.apache.ivyde.feature-2.0.0.alpha1.zip. As an easy fix, I did not  
tried to include ivy binaries into the ivyde feature zip, I just make  
the build create another zip, the ivy feature zip  
org.apache.ivy.feature-2.0.0.beta2.zip. Actually I think that this  
part of the build should probably be transfered to the Ivy build, so  
that the Ivy feature is released with every Ivy release.

Your vote:
+1 : you agree with the release
+0 : you agree but the next release should contain some fixes
-1 : you don't agree, there is a blocker issue with the release

so +1 for me (non binding)

Nicolas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy svn breaks ant-contrib svn

[Maarten Coene]

Yes,

I changed that recently. IvyAntSettings is now a DataType again...
They should use the IvyConfigure task instead.

Maarten




- Original Message 
From: Stefan Bodewig <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Monday, July 14, 2008 9:37:03 AM
Subject: Ivy svn breaks ant-contrib svn

Hi,

just a quick note from Gump


Since I'm not familiar enough with either Ivy or ant-contrib's usage
of it, I can't say who's wrong.  It looks as if ant-contrib expects
IvyAntSettings to extends Task.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy svn breaks ant-contrib svn

[Maarten Coene]

Just a wild guess, but maybe you could use IvyAntSettings again (like your 
original code was), but instead of calling the execute method you can register 
it yourself as Reference in the Project, something like:

IvyAntSettings settings = new IvyAntSettings();
settings.setXXX...
getProject().addReference(settingsId, settings);

Maarten




- Original Message 
From: Stefan Bodewig <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Tuesday, July 15, 2008 2:13:10 PM
Subject: Re: Ivy svn breaks ant-contrib svn

On Tue, 15 Jul 2008, Xavier Hanin <[EMAIL PROTECTED]> wrote:

> On Tue, Jul 15, 2008 at 9:23 AM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> 
> > On Tue, 15 Jul 2008, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> >
> > > On Tue, Jul 15, 2008 at 8:53 AM, Stefan Bodewig <[EMAIL PROTECTED]>
> > wrote:
> > >
> > > > Ant-contrib also invokes setId() on the task, which works fine with
> > > > Ivy 2.0.0beta2 but fails with trunk.
> > > >
> > > > Could you please re-add the setid method?
> > >
> > > setId is now setSettingsId on IvyConfigure, which is more in
> > > conformance with Ant, since we are not setting the id of the
> > > task, but of the underneath datatype.
> >
> > OK, what can ant-contrib do if it wants to compile against Ivy
> > 2.0.0beta2 and trunk with the same codebase?
> 
> This is not straightforward, since we broke the API.

Right, that's why Gump finds it 8-)

Maybe you could throw in a deprecated setId() method that delegated to
setSettingsId()?  At least for the next beta so ant-contrib has a
stable base to work from without resorting to reflection.

I looked into the code to see what the id is used for.  It is later
used as the argument for IvyCacheFileset.setSettingsRef - this
wouldn't work with a reference to the task but would require a
reference to the settings, which now would exactly be what
setSettingsId creates, right?

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ivy junit tests

[Maarten Coene]

For some reason, not all junit tests were executed when running "ant test".
I've changed this, but now the ChainResolverTest fails (something with the 
cache?). 

I don't know if we broke something or if the test is wrong. I don't see it at 
the moment...

regards,
Maarten



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r679208 - /ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/HttpClientHandler.java

[Maarten Coene]

I agree,

The goal is to have one single instance of HttpClient here to be able to reuse 
the connections.
At the moment, the HttpClientHandler isn't a singleton, so the easiest way for 
me was to make it static.

But maybe we can wait to see if the change solves the problem. If it doesn't, 
we can revert it, but if it solves to problem, we can refactor it to some 
cleaner solution.

Maarten




- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Thursday, July 24, 2008 9:08:32 AM
Subject: Re: svn commit: r679208 - 
/ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/HttpClientHandler.java

On Thu, Jul 24, 2008 at 12:06 AM, <[EMAIL PROTECTED]> wrote:

> Author: maartenc
> Date: Wed Jul 23 15:06:48 2008
> New Revision: 679208
>
> URL: http://svn.apache.org/viewvc?rev=679208&view=rev
> Log:
> Attempt to fix connection leak reported in IVY-854 by caching the
> HttpClient instance.
>
> Modified:
>
>  ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/HttpClientHandler.java
>
> Modified:
> ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/HttpClientHandler.java
> URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/HttpClientHandler.java?rev=679208&r1=679207&r2=679208&view=diff
>
> ==
> ---
> ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/HttpClientHandler.java
> (original)
> +++
> ant/ivy/core/trunk/src/java/org/apache/ivy/util/url/HttpClientHandler.java
> Wed Jul 23 15:06:48 2008
> @@ -33,6 +33,7 @@
>  import org.apache.commons.httpclient.HttpException;
>  import org.apache.commons.httpclient.HttpMethodBase;
>  import org.apache.commons.httpclient.HttpStatus;
> +import org.apache.commons.httpclient.MultiThreadedHttpConnectionManager;
>  import org.apache.commons.httpclient.UsernamePasswordCredentials;
>  import org.apache.commons.httpclient.auth.AuthPolicy;
>  import org.apache.commons.httpclient.methods.GetMethod;
> @@ -61,6 +62,8 @@
> private String proxyPasswd = null;
>
> private HttpClientHelper httpClientHelper;
> +
> +private static HttpClient httpClient;


I'm not sure reusing always the same (static) instance of httpClient is
safe. In the context of IvyDE, we will have the same instance of httpClient
whatever the number of settings we use. I know we have other similar
problems about using static stuff which shouldn't be, but I dislike
introducing new ones.

WDYT?

Xavier


>
> public HttpClientHandler() {
> configureProxy();
> @@ -204,28 +207,39 @@
> }
>
> private HttpClient getClient(URL url) {
> -HttpClient client = new HttpClient();
> -
> -List authPrefs = new ArrayList(2);
> -authPrefs.add(AuthPolicy.DIGEST);
> -authPrefs.add(AuthPolicy.BASIC);
> -// Exclude the NTLM authentication scheme because it is not
> supported by this class
> -client.getParams().setParameter(AuthPolicy.AUTH_SCHEME_PRIORITY,
> authPrefs);
> -
> -if (useProxy()) {
> -client.getHostConfiguration().setProxy(proxyHost, proxyPort);
> -if (useProxyAuthentication()) {
> -client.getState().setProxyCredentials(proxyRealm,
> proxyHost,
> -new UsernamePasswordCredentials(proxyUserName,
> proxyPasswd));
> +if (httpClient == null) {
> +final MultiThreadedHttpConnectionManager connManager = new
> MultiThreadedHttpConnectionManager();
> +httpClient = new HttpClient(connManager);
> +
> +Runtime.getRuntime().addShutdownHook(new Thread(new Runnable()
> {
> +public void run() {
> +connManager.shutdown();
> +}
> +}));
> +
> +List authPrefs = new ArrayList(2);
> +authPrefs.add(AuthPolicy.DIGEST);
> +authPrefs.add(AuthPolicy.BASIC);
> +// Exclude the NTLM authentication scheme because it is not
> supported by this class
> +
>  httpClient.getParams().setParameter(AuthPolicy.AUTH_SCHEME_PRIORITY,
> authPrefs);
> +
> +if (useProxy()) {
> +httpClient.getHostConfiguration().setProxy(proxyHost,
> proxyPort);
> +if (useProxyAuthentication()) {
> +httpClient.getState().setProxyCredentials(proxyRealm,
> proxyHost,
> +new UsernamePasswordCredentials(proxyUserName,
> proxyPasswd));
> +}
> }
> }
> +
> Credentials c = getCredentials(url);
> if (c != null) {
> Message.debug("found credentials for " + url + ": " + c);
> -client.getState().setCredentials(c.getRealm(), c.getHost(),
> +httpClient.getState().setCredentials(c.getRealm(),
> c.getHost(),
> new UsernamePasswordCredentials(c.getUserName(),
> c.getPasswd()));
> }
> -return client;
> +
> +return httpClient;
> }
>
> private bo

Re: PatternVersionMatcher in Ivy code base

[Maarten Coene]

Xavier,

I've looked at the code, and I can't remember writing such a thing and I can't 
remember using it.

The svn history logs indicates I've added the code, so I can only think of 3 
options:
- there must be something wrong with my memory
- there went something wrong importing the svn history from jayasoft to apache
- I've added it on request of someone else who maybe posted it on the jayasoft 
forums (I've checked JIRA, but didn't find anything)

Maarten




- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Monday, August 4, 2008 8:22:38 PM
Subject: PatternVersionMatcher in Ivy code base

Hi,

While answering a question from a user on the user ml, I've checked the code
to see if we have a version matcher able to work with regular expression, as
I remembered sg like this have been developed before. I've found
PatternVersionMatcher. But it seems this is not documented, not tested and
not even declared in our default typedef.properties. According to the svn
log, Maarten, you seem to be the one who has checked in this code. Do you
remember your use case? Do you have any hint on how it is used? According to
the code there's something with parenthesis and arguments given to the
revision and the matcher. But at least an example would help. And since it
seems to be very powerful, adding documentation about it would be nice too -
a kind of new feature, despite it's in the code base for 2 years now :-).

Xavier

-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy Broken unit test

[Maarten Coene]

I only have a failing ChainResolverTest.

Maarten



- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Tuesday, August 5, 2008 6:44:35 PM
Subject: Re: Ivy Broken unit test

On Tue, Aug 5, 2008 at 3:56 PM, Gilles Scokart <[EMAIL PROTECTED]> wrote:

> I have some unit test failing :
>
> Test org.apache.ivy.ant.IvyAntSettingsTest FAILED
> Test org.apache.ivy.ant.IvyConfigureTest FAILED
> Test org.apache.ivy.ant.IvyTaskTest FAILED
> Test org.apache.ivy.plugins.resolver.ChainResolverTest FAILED
> Test org.apache.ivy.core.NormalRelativeUrlResolverTest FAILED
>
> Gump seems OK : http://vmgump.apache.org/gump/public/ivy/index.html
>
> Am I the only one (I'm using ibm jvm 1.5 on cygwin, but up to now I
> didn't had any problem with this set up).

On my box (ubuntu + ant 1.7 + java 6) last night I had problem with only two
unit tests: ChainResolverTest and PackagerResolverTest. ChainResolverTest
failure has been reported by Maarten after reactivating the test, I have to
investigate but haven't found time yet. For PackagerResolver it may be due
to my box, I haven't checked.

Xavier


>
>
> I will try with older source base to see where it failed.
>
> --
> Gilles Scokart
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r683187 - /ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java

[Maarten Coene]

Xavier,

I think this is an excellent idea :-)

Maarten



- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, August 6, 2008 1:04:45 PM
Subject: Re: svn commit: r683187 - 
/ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java

On Wed, Aug 6, 2008 at 11:38 AM, Gilles Scokart <[EMAIL PROTECTED]> wrote:

> Could someone retest that in an other environment (I only have access
> to an IBM JVM).

I'm not on my dev box now, so I can't confirm it works, but I see no reason
why it would fail. That being said, I think it would be cleaner to extract
this "trick" in a helper method. Maybe sg on FileUtil:
FileUtil#toURL(File file) {
   return file.toURI().toURL();
}

This would help documenting why we use this trick, and fix everything at
once if we later need another way to get an URL from a File.

Xavier


>
> Other fix will follow.
>
> Gilles
>
>
> 2008/8/6  <[EMAIL PROTECTED]>:
> > Author: gscokart
> > Date: Wed Aug  6 02:10:07 2008
> > New Revision: 683187
> >
> > URL: http://svn.apache.org/viewvc?rev=683187&view=rev
> > Log:
> > fix unit test on IBM JVM (probably broken by IVY-868)
> >
> > Modified:
> >ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java
> >
> > Modified:
> ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java
> > URL:
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java?rev=683187&r1=683186&r2=683187&view=diff
> >
> ==
> > --- ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java
> (original)
> > +++ ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java Wed
> Aug  6 02:10:07 2008
> > @@ -50,7 +50,7 @@
> > assertEquals(new
> File("test/repositories/ivysettings.xml").getAbsolutePath().toUpperCase(),
> > new File((String)
> settings.getVariables().getVariable("ivy.settings.file")).getAbsolutePath()
> > .toUpperCase());
> > -assertEquals(new
> File("test/repositories/ivysettings.xml").toURL().toExternalForm()
> > +assertEquals(new
> File("test/repositories/ivysettings.xml").toURI().toURL().toExternalForm()
> > .toUpperCase(), ((String)
> settings.getVariables().getVariable("ivy.settings.url"))
> > .toUpperCase());
> > assertEquals(new
> File("test/repositories").getAbsolutePath().toUpperCase(),
> > @@ -82,7 +82,7 @@
> > assertEquals(new File("build/cache"),
> settings.getDefaultCache());
> > assertEquals(new
> File("test/repositories/ivysettings.xml").getAbsolutePath(), settings
> > .getVariables().getVariable("ivy.settings.file"));
> > -assertEquals(new
> File("test/repositories/ivysettings.xml").toURL().toExternalForm(),
> > +assertEquals(new
> File("test/repositories/ivysettings.xml").toURI().toURL().toExternalForm(),
> > settings.getVariables().getVariable("ivy.settings.url"));
> > assertEquals(new File("test/repositories").getAbsolutePath(),
> settings.getVariables().getVariable(
> > "ivy.settings.dir"));
> >
> >
> >
>
>
>
> --
> Gilles Scokart
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r683187 - /ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java

[Maarten Coene]

The tests are still running ok for me on Windows

Maarten




- Original Message 
From: Gilles Scokart <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Wednesday, August 6, 2008 11:38:57 AM
Subject: Re: svn commit: r683187 - 
/ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java

Could someone retest that in an other environment (I only have access
to an IBM JVM).

Other fix will follow.

Gilles


2008/8/6  <[EMAIL PROTECTED]>:
> Author: gscokart
> Date: Wed Aug  6 02:10:07 2008
> New Revision: 683187
>
> URL: http://svn.apache.org/viewvc?rev=683187&view=rev
> Log:
> fix unit test on IBM JVM (probably broken by IVY-868)
>
> Modified:
>ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java
>
> Modified: ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java
> URL: 
> http://svn.apache.org/viewvc/ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java?rev=683187&r1=683186&r2=683187&view=diff
> ==
> --- ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java 
> (original)
> +++ ant/ivy/core/trunk/test/java/org/apache/ivy/ant/IvyTaskTest.java Wed Aug  
> 6 02:10:07 2008
> @@ -50,7 +50,7 @@
> assertEquals(new 
> File("test/repositories/ivysettings.xml").getAbsolutePath().toUpperCase(),
> new File((String) 
> settings.getVariables().getVariable("ivy.settings.file")).getAbsolutePath()
> .toUpperCase());
> -assertEquals(new 
> File("test/repositories/ivysettings.xml").toURL().toExternalForm()
> +assertEquals(new 
> File("test/repositories/ivysettings.xml").toURI().toURL().toExternalForm()
> .toUpperCase(), ((String) 
> settings.getVariables().getVariable("ivy.settings.url"))
> .toUpperCase());
> assertEquals(new 
> File("test/repositories").getAbsolutePath().toUpperCase(),
> @@ -82,7 +82,7 @@
> assertEquals(new File("build/cache"), settings.getDefaultCache());
> assertEquals(new 
> File("test/repositories/ivysettings.xml").getAbsolutePath(), settings
> .getVariables().getVariable("ivy.settings.file"));
> -assertEquals(new 
> File("test/repositories/ivysettings.xml").toURL().toExternalForm(),
> +assertEquals(new 
> File("test/repositories/ivysettings.xml").toURI().toURL().toExternalForm(),
> settings.getVariables().getVariable("ivy.settings.url"));
> assertEquals(new File("test/repositories").getAbsolutePath(), 
> settings.getVariables().getVariable(
> "ivy.settings.dir"));
>
>
>



-- 
Gilles Scokart

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Fix for IVY-905

[Maarten Coene]

Xavier,

you've merged that fix into the 2.0.x branch. Does this mean it will be 
included in the 2.0.0 final release?

Maarten




- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, September 17, 2008 9:03:06 AM
Subject: Re: [VOTE] Ivy 2.0.0-rc1 Release

On Tue, Sep 16, 2008 at 10:38 PM, Xavier Hanin <[EMAIL PROTECTED]>wrote:

> It seems IVY-905 is a blocking issue in this first attempt for rc1, so I'll
> have to make a new attempt for rc1 with Maarten's fix. We'll try to find a
> fix for the cygwin related issues too in the same time before making this
> new attempt. I should cast a new vote tomorrow, so wait for it before
> reviewing.
>
Ok, I think maarten and I analysis yesterday evening was made too quickly.
the fix for IVY-905 Maarten checked in is only a fix for the Configurator
class, which has no impact on how Ivy behave. Indeed, the fix impact the
FileResolver used by default in Configurator, but the only place where
Configurator is used in Ivy is in XmlSettingsParser, where the file resolver
is immediately set to another FileResolver implementation, which works
properly (except maybe on cygwin when you use unix like paths, but it seems
Java is not aware of the cygwin environment).

Thus I don't think this require a new attempt for 2.0.0-rc1, we can go on
with the binaries I've uploaded yesterday and on which I already cast a
vote.

That being said, this discussion has added noise to the vote thread, so if
somebody think we'd better start a new vote (loosing one day for the final
decision), let me know as soon as possible.

Xavier


>
> Xavier
>
> On Tue, Sep 16, 2008 at 9:56 AM, Xavier Hanin <[EMAIL PROTECTED]>wrote:
>
>> I have built a release candidate for Ivy 2.0.0-rc1
>>
>> You can download it from this URL:
>> http://people.apache.org/~xavier/ivy/staging/2.0.0-rc1/
>>
>> A maven 2 staging repo with this release is available here:
>> http://people.apache.org/~xavier/m2-staging-repo/
>> A staging eclipse update site with this release is available here:
>> http://people.apache.org/~xavier/updatesite-staging/
>> The bundle version is 2.0.0.cr1.
>>
>> Do you vote for the release of these binaries?
>>
>> [ ] Yes
>> [ ] No
>>
>> Regards,
>>
>> Xavier, Ivy 2.0.0-rc1 release manager
>>
>
>
>
> --
> Xavier Hanin - Independent Java Consultant
> BordeauxJUG co leader - http://www.bordeauxjug.org/
> Blogger - http://xhab.blogspot.com/
> Apache Ivy Creator - http://ant.apache.org/ivy/
>



-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Ivy 2.0.0-rc1 Release

[Maarten Coene]

+1

Maarten




- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Tuesday, September 16, 2008 9:56:25 AM
Subject: [VOTE] Ivy 2.0.0-rc1 Release

I have built a release candidate for Ivy 2.0.0-rc1

You can download it from this URL:
http://people.apache.org/~xavier/ivy/staging/2.0.0-rc1/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~xavier/m2-staging-repo/
A staging eclipse update site with this release is available here:
http://people.apache.org/~xavier/updatesite-staging/
The bundle version is 2.0.0.cr1.

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Xavier, Ivy 2.0.0-rc1 release manager



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

[Maarten Coene]

If you want this issue to be fixed, please do

- vote for https://issues.apache.org/jira/browse/IVY-736, or
- attach a patch to this issue, or
- attach a junit test to this issue, or
- do all of the things above :-)

Maarten



- Original Message 
From: "Wardrip, Paul" <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, September 18, 2008 10:12:16 PM
Subject: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

In PomModuleDescriptorWriter.java would it be possible to change hard
coded "jar" value that is written for packaging to use the artifact
extension? If I publish something that isn't a jar to a maven
repository, ivy expects it to be a jar when I try to use it as a
dependency of another project.

private static void printModuleId(ModuleDescriptor md, PrintWriter
out) {
ModuleRevisionId mrid = md.getModuleRevisionId();
out.println("  " + mrid.getOrganisation() +
"");
out.println("  " + mrid.getName() +
"");
out.println("  jar");

--to --
  
out.println("  " + artifacts[i].getExt() +
"");


Paul Wardrip
Software Engineer, OpenStream
TANDBERG Television | Part of the Ericsson Group
4500 River Green Parkway | Duluth | GA 30096
Mobile: 770-312-2852 | AIM: paulwardrip
Email: [EMAIL PROTECTED] | www.tandbergtv.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

[Maarten Coene]

Indeed, and an error (or warning) could be thrown if you Ivy module defines an 
artifact having a different name than the module name.
I think there was a JIRA issue as well for supporting more than 1 artifact...

Maarten



- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, September 18, 2008 10:49:40 PM
Subject: Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

On Thu, Sep 18, 2008 at 10:12 PM, Wardrip, Paul <[EMAIL PROTECTED]>wrote:

> In PomModuleDescriptorWriter.java would it be possible to change hard
> coded "jar" value that is written for packaging to use the artifact
> extension? If I publish something that isn't a jar to a maven
> repository, ivy expects it to be a jar when I try to use it as a
> dependency of another project.
>
>private static void printModuleId(ModuleDescriptor md, PrintWriter
> out) {
>ModuleRevisionId mrid = md.getModuleRevisionId();
>out.println("  " + mrid.getOrganisation() +
> "");
>out.println("  " + mrid.getName() +
> "");
>out.println("  jar");
>
> --  to --
>
>out.println("  " + artifacts[i].getExt() +
> "");


The only problem I see to implement it is that in Ivy you can have multiple
artifacts, while in Maven you have only one (well, you can have more with
qualifiers, but you have one main artifact). So the patch is not that easy,
but it could be at least improved when only one artifact is published by the
Ivy module.

Xavier


>
> 
> Paul Wardrip
> Software Engineer, OpenStream
> TANDBERG Television | Part of the Ericsson Group
> 4500 River Green Parkway | Duluth | GA 30096
> Mobile: 770-312-2852 | AIM: paulwardrip
> Email: [EMAIL PROTECTED] | www.tandbergtv.com
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Some Ivy POM problems

[Maarten Coene]

I've applied your patches into SVN and the 2.0.x branch.

They won't be included into RC1 because we already created the release, the RC1 
announcement will be sent very soon...
If we will create a RC2 is not certain at the moment and it will be discussed 
later on this mailing list.

Maarten




- Original Message 
From: Tom Widmer <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Tuesday, September 23, 2008 1:42:33 PM
Subject: Some Ivy POM problems

https://issues.apache.org/jira/browse/IVY-913
https://issues.apache.org/jira/browse/IVY-914

I've attached patches for both. Any chance of getting them into RC1 (or 
failing that RC2?)?

Thanks,

Tom


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [DISCUSS] Ivy 2.0.0-rc1 announcement

[Maarten Coene]

Looks fine to me...

Maarten



- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Tuesday, September 23, 2008 4:42:17 PM
Subject: [DISCUSS] Ivy 2.0.0-rc1 announcement

Hi,
The vote for Ivy 2.0.0-rc1 is now over (I'll send another e-mail with the
result), so it's time to make the final steps for the release. It includes
announcing the release, so what do you think of this announcement:

 - The Apache Ivy project is pleased to announce its
2.0.0 rc 1 version, the first 2.0.0 final release candidate.

Ivy is a tool for managing (recording, tracking, resolving and
reporting) project dependencies, characterized by flexibility,
configurability, and tight integration with Apache Ant.

This is a release candidate for 2.0.0 final, meaning that no changes
except bug fixes will occur before this release candidate and 2.0.0 final.
Problems found at this phase can be fixed in the final release, so now
is a good time to download and use it. If no outstanding bugs are reported
in the coming weeks, this release candidate will be promoted as 2.0.0 final.

Key changes in this 2.0.0-rc1 version are
* enhanced Maven2 compatibility, with several bug fixes and more
  pom features covered
* better and more homogeneous relative paths handling
* better support for local builds
* 80+ bug fixes as documented in Jira and in the release notes

Issues should be reported to:
https://issues.apache.org/jira/browse/IVY

Download the 2.0.0-rc1 release files at:
http://ant.apache.org/ivy/download.cgi

More information can be found on the Ivy website:
http://ant.apache.org/ivy/

Regards,
Xavier Hanin (2.0.0-rc1 release mgr)


WDYT?

Xavier
-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy SFTP resolver - java.net.MalformedURLException

[Maarten Coene]

I'm a bit confused here, you talk about the SFTP resolver, but your log shows 
only http URLs?
Could you try it again with Ivy RC1, it contains some improvements for such 
kind of urls with "strange" characters.

oh and please post such kind of questions to the ivy-user mailinglist in the 
future...

Maarten




- Original Message 
From: Wszeb <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Wednesday, September 24, 2008 5:28:49 PM
Subject: Ivy SFTP resolver - java.net.MalformedURLException


Hi! 

I have such a disaster with Ivy SFTP resolver and "tag-20080924.16:47-dev.+"
revision constraint:

no cached resolved revision for
com.company#IvyPortletsCore;tag-20080924.16:47-dev.+
[ivy:resolve] no cached resolved revision for
com.company#IvyPortletsCore;tag-20080924.16:47-dev.+
[ivy:resolve] tried
http://10.132.5.11/ivy-repos/little-john/com.company/IvyPortletsCore/tag-20080924.16:47-dev.+/ivy-tag-20080924.16:47-dev.+.xml
[ivy:resolve] CLIENT ERROR: Not Found
url=http://10.132.5.11/ivy-repos/little-john/com.company/IvyPortletsCore/tag-20080924.16:47-dev.+/ivy-tag-20080924.16:47-dev.+.xml
[ivy:resolve] tried
http://10.132.5.11/ivy-repos/little-john/com.company/IvyPortletsCore/[revision]/ivy-[revision].xml
[ivy:resolve] problem while listing resources in
http://10.132.5.11/ivy-repos/little-john/com.company/IvyPortletsCore/ with
little-john:
[ivy:resolve]  java.net.MalformedURLException unknown protocol:
tag-20080924.15

Is it a bug or is ":" illegal in this context?

Wszebor.
-- 
View this message in context: 
http://www.nabble.com/Ivy-SFTP-resolver---java.net.MalformedURLException-tp19651441p19651441.html
Sent from the Ant - Dev mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Illegal XML in Maven POM's

[Maarten Coene]

(moved discussion from ivy-user mailing-list to here)

Xavier,

I already have a patch ready on my machine (it just needs some cleanup and 
junit testing).
Shall I finish and commit it?

I
agree with you that the better solution would be that the maven people
only post valid XML files into their repositories, but on the other
hand, I think that we should try to make Ivy as tolerant as maven: if
maven can parse it, Ivy should also be able to parse it too. Otherwise,
people will get into trouble when having such kind of dependencies for
which they don't have any control on the pom... and what with invalid
XML's on public maven repositories outside the "control" of apache?

Maarten



- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Monday, September 29, 2008 9:03:59 AM
Subject: Re: Illegal XML in Maven POM's

On Fri, Sep 26, 2008 at 9:19 PM, Maarten Coene <[EMAIL PROTECTED]>wrote:

> Please open a new Ivy JIRA issue.

I don't think we should open an issue for that. Well, maybe we can open an
issue for consistency, but mark it as invalid. Indeed I don't think
accepting something which is not valid XML makes any sense, it's just too
much work. And maven guys themselves agree that their poms should be valid
xml, there's already been a discussion on the [EMAIL PROTECTED] list
about that. So I don't see much we can do except loby maven guys to make
sure they publish only valid xml poms.

Xavier


>
>
> Maarten
>
>
>
>
> - Original Message 
> From: Hans Dockter <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Sent: Friday, September 26, 2008 4:02:09 PM
> Subject: Illegal XML in Maven POM's
>
> Hi,
>
> Maven seems to generate illegal XML for its pom's. For example if the
> developers have a special character in there name.
>
> Two examples:
>
> http://repo1.maven.org/maven2/qdox/qdox/1.6/qdox-1.6.pom
> http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.4/
> plexus-1.0.4.pom
>
> I have run lately a couple of times into problems with this. Maven
> itself seems to be happy with that. Ivy definitely not:
>
> [ivy:retrieve]  ERRORS
> [ivy:retrieve]  The entity "oslash" was referenced, but not declared.
>
> I had no time to check the Maven Jira if this is a known bug. My
> posting is just for pointing this out. I'm not sure how far Ivy wants
> to go with the Maven warts reverse engineering ;)
>
> - Hans
>
> --
> Hans Dockter
> Gradle Project lead
> http://www.gradle.org
>
>
>
>


-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [jira] Commented: (IVYDE-51) IvyDE doesn't set the ${basedir} property

[Maarten Coene]

I have some questions:

What is the meaning of this ${basedir} property in Ivy?
Is it different than the ${basedir} property from Ant?
And why have 2 properties which have the same value (${ivy.basedir} and 
${basedir}) ?

Maarten




- Original Message 
From: Xavier Hanin <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Wednesday, October 1, 2008 8:06:55 AM
Subject: Re: [jira] Commented: (IVYDE-51) IvyDE doesn't set the ${basedir} 
property

On Tue, Sep 30, 2008 at 9:28 PM, Nicolas Lalevée <[EMAIL PROTECTED]
> wrote:

>
> Le 22 sept. 08 à 10:08, Nicolas Lalevée (JIRA) a écrit :
>
>
>>   [
>> https://issues.apache.org/jira/browse/IVYDE-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633165#action_12633165
>> ]
>>
>> Nicolas Lalevée commented on IVYDE-51:
>> --
>>
>> Yes, you can use {{${ivy.basedir}}}. But I don't think we can close this
>> issue yet, the {{basedir}} property should be set. And the remaining
>> question is where it should be set. In IvyDE, or in Ivy on the call of
>> {{IvySetting#setBaseDir(File)}} ?
>>
>
> I think it would be a good idea to do it in Ivy.
> Any objection ?

No objection, as long as you don't override it if already defined.

Xavier


>
>
> Nicolas
>
>
>>
>>  IvyDE doesn't set the ${basedir} property
>>> -
>>>
>>>   Key: IVYDE-51
>>>   URL: https://issues.apache.org/jira/browse/IVYDE-51
>>>   Project: IvyDE
>>>Issue Type: Improvement
>>>Components: classpath container
>>>  Affects Versions: 2.0.0.alpha1
>>>  Reporter: Maarten Coene
>>>
>>> IvyDE doesn't specify the ${basedir} property when resolving the
>>> dependencies.
>>> This means that it's not possible to resolve jar files in a [project]/lib
>>> directory.
>>> For instance, the following resolver doesn't work:
>>> {code}
>>> 
>>> >> pattern="${ivy.project.dir}/lib/[artifact](-[revision]).[ext]" />
>>> 
>>> {code}
>>> Maarten
>>>
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Next step in Ivy 2.0 release process

[Maarten Coene]

Hi,

Ivy-2.0.0-RC1 is out for some time now. What will be the next step?

- create a new RC2 release containing some (or all) of the bugfixes which have 
been committed into SVN trunk and maybe some open issues which aren't fixed yet
- create a 2.0.0 final release based on RC1

I'm in favor for a new RC2 containing everything from SVN trunk. What do others 
think?

Maarten



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Java version required for trunk

[Maarten Coene]

We are also still using JDK1.4.
We"ll probably upgrade to Java 6 next year after we have solved some 
incompatibilities between JDK1.4 and JDK6

Maarten



- Original Message 
From: Stefan Bodewig <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Wednesday, October 15, 2008 5:02:40 PM
Subject: Re: Java version required for trunk

On Wed, 15 Oct 2008, Jeffrey E. Care <[EMAIL PROTECTED]> wrote:

> I think moving to 1.4 is fine; I'm actually kind of surprised that
> we've even go that low. Do we have a sense that people are still out
> there in the wild using JDK 1.4?

I'm one of them myself, stuck with a customer who has finally migrated
to WebSphere AS 6.0 and won't move to 6.1 in the foreseeable future.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Next step in Ivy 2.0 release process

[Maarten Coene]

ok, unless someone else volunteers, I'll try to make a RC2 next week.

There are still some open issues I want to include in this release:
- IVY-943: Allow authentication credentials to be specified in settings file. 
-> or should I not add it because it's not really a bug, but the provided code 
change is very simple and very low-risk
- IVY-881: Ivy incorrectly searches for an artifact if it contains / in the 
name -> only if there is a patch ready before I start creating RC2
- IVY-931: What to do if Ivy can't find the parent of a POM -> if no-one 
objects, I let Ivy fail if the parent POM cannot be found

Are there other open issues that should make it into RC2?

Maarten




- Original Message 
From: Gilles Scokart <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, October 16, 2008 10:39:29 AM
Subject: Re: Next step in Ivy 2.0 release process

2008/10/15 Maarten Coene <[EMAIL PROTECTED]>:
> Hi,
>
> Ivy-2.0.0-RC1 is out for some time now. What will be the next step?
>
> - create a new RC2 release containing some (or all) of the bugfixes which 
> have been committed into SVN trunk and maybe some open issues which aren't 
> fixed yet
> - create a 2.0.0 final release based on RC1
>
> I'm in favor for a new RC2 containing everything from SVN trunk. What do 
> others think?

+1.  Only bug fixing have been commited to the trunk.  And I think
some justify a second RC.



-- 
Gilles Scokart

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Next step in Ivy 2.0 release process

[Maarten Coene]

Please do, I'll try to make a new release within the next couple of days...

Maarten




- Original Message 
From: Nicolas Lalevée <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Tuesday, October 21, 2008 9:23:40 AM
Subject: Re: Next step in Ivy 2.0 release process

Sorry for the late reply, I nearly forgot about IVY-953. I think it should be 
integrated too. I can have it fix quickly.

Nicolas




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ivy 2.0.0 RC2 - status

[Maarten Coene]

Hi all,

I've started creating Ivy 2.0.0 RC2 a couple of days ago, but I have some delay 
:-(
I'm almost finished I think, just need to create the eclipse bundle before I 
start a vote.

Because I don't have time today and tomorrow to finish it, I'll post the 
download link now so you could already check that I didn't forget anything.

- download URL: http://people.apache.org/~maartenc/ivy/staging/2.0.0-rc2/
- Maven2 repo: http://people.apache.org/~maartenc/m2-staging-repo/

Maarten



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[VOTE] Ivy 2.0.0-rc2 Release

[Maarten Coene]

I have built a second release candidate for Ivy 2.0.0

You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.0.0-rc2/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~maartenc/m2-staging-repo/

A staging eclipse update site with this release is available here:
http://people.apache.org/~maartenc/updatesite-staging/
The bundle version is 2.0.0.cr2.

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Maarten Coene, 
Ivy 2.0.0-rc2 release manager 



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Ivy 2.0.0-rc2 Release

[Maarten Coene]

ok, I've added my public key to the KEYS file.
Could you try to verify the signed artifacts again?

Maarten




- Original Message 
From: Nicolas Lalevée <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Sunday, November 2, 2008 4:56:09 PM
Subject: Re: [VOTE] Ivy 2.0.0-rc2 Release

I am not able to verify the signed artifacts as I don't have your  
public key, and I cannot find it in the ant KEYS file 
(http://www.apache.org/dist/ant/KEYS 
).
Have you published it somewhere else ?
Though every else worked fine for me for this release.

Nicolas

Le 28 oct. 08 à 23:53, Maarten Coene a écrit :

> I have built a second release candidate for Ivy 2.0.0
>
> You can download it from this URL:
> http://people.apache.org/~maartenc/ivy/staging/2.0.0-rc2/
>
> A maven 2 staging repo with this release is available here:
> http://people.apache.org/~maartenc/m2-staging-repo/
>
> A staging eclipse update site with this release is available here:
> http://people.apache.org/~maartenc/updatesite-staging/
> The bundle version is 2.0.0.cr2.
>
> Do you vote for the release of these binaries?
>
> [ ] Yes
> [ ] No
>
> Regards,
>
> Maarten Coene,
> Ivy 2.0.0-rc2 release manager
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Ivy 2.0.0-rc2 Release

[Maarten Coene]

Almost forgot to vote myself, so here is mine +1

Maarten



- Original Message 
From: Maarten Coene <[EMAIL PROTECTED]>
To: ant-dev 
Sent: Tuesday, October 28, 2008 11:53:50 PM
Subject: [VOTE] Ivy 2.0.0-rc2 Release

I have built a second release candidate for Ivy 2.0.0

You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.0.0-rc2/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~maartenc/m2-staging-repo/

A staging eclipse update site with this release is available here:
http://people.apache.org/~maartenc/updatesite-staging/
The bundle version is 2.0.0.cr2.

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Maarten Coene, 
Ivy 2.0.0-rc2 release manager 



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[RESULT][VOTE] Ivy 2.0.0-rc2 Release

[Maarten Coene]

The vote is over for the Ivy 2.0.0-rc2 release. With 4 binding +1, the vote has 
passed.
I'll proceed to make the release official in the coming days.

Maarten



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

problem updating the ivy website

[Maarten Coene]

I've committed the Ivy 2.0.0-rc2 website in svn: 
https://svn.apache.org/repos/asf/ant/ivy/site/target/
When I want to update it in /www/ant.apache.org/ivy I get the following error:

[EMAIL PROTECTED] /www/ant.apache.org/ivy]$ svn up
svn: Can't open file 'history/trunk/settings/.svn/lock': Permission denied

Xavier: can you update the site or modify the permissions?

regards
Maarten



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANNOUNCE] Apache Ivy 2.0.0-rc2 released

[Maarten Coene]

Nov 4, 2008 - The Apache Ivy project is pleased to announce the
release of Ivy 2.0.0-rc2, the second release candidate for Ivy 2.0.0.

Ivy is a tool for managing (recording, tracking, resolving and
reporting) project dependencies, characterized by flexibility,
configurability, and tight integration with Apache Ant.

This is a release candidate for 2.0.0 final, meaning that no changes 
except bug fixes will occur between this release candidate and 2.0.0 final.
Problems found at this phase can be fixed in the final release, so now 
is a good time to download and use it. If no outstanding bugs are reported
in the coming weeks, this release candidate will be promoted as the 2.0.0 
final release.

Key changes in this 2.0.0-rc2 version are
* enhanced Maven2 compatibility, with several bug fixes
* 20+ bug fixes as documented in Jira and in the release notes

Issues should be reported to:
https://issues.apache.org/jira/browse/IVY

Download the 2.0.0-rc2 release files at:
http://ant.apache.org/ivy/download.cgi

More information can be found on the Ivy website:
http://ant.apache.org/ivy/

Regards,
Maarten Coene (2.0.0-rc2 release manager)



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [ANNOUNCE] Apache Ivy 2.0.0-rc2 released

[Maarten Coene]

that would be cool indeed...

But I think we can release Ivy-2.0 final within 2 or 3 weeks if no serious bugs 
are reported against RC2.
Maybe we should only announce the final release on ant.apache.org ? 

WDYT?

Maarten




- Original Message 
From: Stefan Bodewig <[EMAIL PROTECTED]>
To: dev@ant.apache.org
Sent: Thursday, November 6, 2008 11:06:36 AM
Subject: Re: [ANNOUNCE] Apache Ivy 2.0.0-rc2 released

Congrats,

you may want to announce this on the ant.apache.org homepage as well.
Let us know if you need a hand.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: IvyDE 2.0 roadmap

[Maarten Coene]

Sounds good to me

Maarten




- Original Message 
From: Nicolas Lalevée <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Monday, November 10, 2008 11:15:48 PM
Subject: IvyDE 2.0 roadmap

I would like to discuss about the next release of IvyDE.

The last release of IvyDE was made 4 months ago, there are some important bug 
fixes that make IvyDE a lot more stable, so I think it is a good time to get an 
IvyDE release now.
Thought I don't think that that next release is enough tested to be flagged as 
"2.0 final", I think a "beta" state is more appropriate, there are still opened 
and unresolved bugs. And the current implementation of the "resolve in 
workspace" is a little bit hacky. I would see that release as a milestone in a 
stable 2.0 roadmap.

For that beta release, I would like to take time to include IVYDE-120 (make 
IvyDE work in Eclipse 3.2), and also IVYDE-119 (little refactoring of the UI, 
maybe together with IVYDE-106 (choose the configuration used during retrieve)).

After that beta out, I think we should focus then on a 2.0 final, making every 
bugs fixed, having a correct "resolve in workspace" implementation.

WDYT ?

Nicolas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] IvyDE 2.0.0.beta1 Release

[Maarten Coene]

I'm getting an error when trying to update the already installed IvyDE plugin.
I'm using Eclipse 3.4.0 and tried both 
http://people.apache.org/~hibou/staging/updatesite and 
http://people.apache.org/~hibou/test-updatesite/

This is the information I could find in the Eclipse .log file

!ENTRY org.eclipse.equinox.p2.metadata.repository 2 0 2008-11-27 22:59:53.890
!MESSAGE Error parsing metadata repository
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 10, column 91: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 10, column 91: Illegal value for attribute "url" of 
element "repository": null
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 11, column 91: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 11, column 91: Illegal value for attribute "url" of 
element "repository": null
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 12, column 90: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 12, column 90: Illegal value for attribute "url" of 
element "repository": null
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 13, column 90: Missing required attribute in 
"repository": url
!SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2008-11-27 22:59:53.890
!MESSAGE Error at line 13, column 90: Illegal value for attribute "url" of 
element "repository": null

!ENTRY org.eclipse.equinox.p2.engine 4 4 2008-11-27 23:00:22.142
!MESSAGE An error occurred during provisioning.
!SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2008-11-27 
23:00:22.142
!MESSAGE Failed to prepare partial IU: [R]org.apache.ivy 2.0.0.cr2.


Maarten




- Original Message 
From: Nicolas Lalevée <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Thursday, November 27, 2008 11:04:34 AM
Subject: [VOTE] IvyDE 2.0.0.beta1 Release

I have built a release candidate for IvyDE 2.0.0.beta1

You can download the distribution from this URL: 
http://people.apache.org/~hibou/ivyde-2.0.0.beta1/ 


And a staging update site has been setup there: 
http://people.apache.org/~hibou/staging/updatesite 


Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Nicolas, IvyDE 2.0.0.beta1 release manager


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] IvyDE 2.0.0.beta1 Release - Take 2

[Maarten Coene]

+1

I did some basic testing with Eclipse 3.5M3 and everything seems to work fine 
:-)

Maarten



- Original Message 
From: Nicolas Lalevée <[EMAIL PROTECTED]>
To: Ant Developers List 
Sent: Monday, December 1, 2008 10:17:00 AM
Subject: [VOTE] IvyDE 2.0.0.beta1 Release - Take 2

I have built a release candidate for IvyDE 2.0.0.beta1. Compared to the first 
version I have just rebuild the updatesite so the packed jar are compatible 
with some java 5 jre.

You can download the distribution from this URL: 
http://people.apache.org/~hibou/ivyde-2.0.0.beta1/

And a staging update site has been setup there: 
http://people.apache.org/~hibou/staging/updatesite

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Nicolas, IvyDE 2.0.0.beta1 release manager

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Releasing Ivy 2.0.0 ?

[Maarten Coene]

Ivy 2.0.0 RC2 is out for some time now. I think that none of the reported 
issues agains RC2 are critical enough to block a 2.0.0 final release.

However, I would like to include the following trivial changes in the 2.0.0 
final release (without making a new RC3 release):
- https://issues.apache.org/jira/browse/IVY-976
- https://issues.apache.org/jira/browse/IVY-960
- https://issues.apache.org/jira/browse/IVY-961
- https://issues.apache.org/jira/browse/IVY-980
- https://issues.apache.org/jira/browse/IVY-965
- https://issues.apache.org/jira/browse/IVY-975

If no-one objects and no-one else volunteers, I'll create the final release 
next week and start a vote for it.

regards,
Maarten


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r727546 - /ant/ivy/core/branches/2.0.0/build-release.xml

[Maarten Coene]

Yes,
I'll do the merge when I'm finished with the 2.0.0 release...

Maarten



- Original Message 
From: Gilles Scokart 
To: dev@ant.apache.org
Sent: Thursday, December 18, 2008 10:33:14 AM
Subject: Re: svn commit: r727546 - 
/ant/ivy/core/branches/2.0.0/build-release.xml

Shouldn't this be done on the trunk ?

Gilles Scokart



2008/12/17  :
> Author: maartenc
> Date: Wed Dec 17 14:23:26 2008
> New Revision: 727546
>
> URL: http://svn.apache.org/viewvc?rev=727546&view=rev
> Log:
> A bit less logging when signing the files
>
> Modified:
>ant/ivy/core/branches/2.0.0/build-release.xml
>
> Modified: ant/ivy/core/branches/2.0.0/build-release.xml
> URL: 
> http://svn.apache.org/viewvc/ant/ivy/core/branches/2.0.0/build-release.xml?rev=727546&r1=727545&r2=727546&view=diff
> ==
> --- ant/ivy/core/branches/2.0.0/build-release.xml (original)
> +++ ant/ivy/core/branches/2.0.0/build-release.xml Wed Dec 17 14:23:26 2008
> @@ -216,13 +216,13 @@
>
>
> file="ivysettings-signtask.xml" />
> -settingsRef="sign.settingsId" transitive="false"
> +settingsRef="sign.settingsId" transitive="false" log="download-only"
>module="commons-openpgp" 
> revision="1.0-SNAPSHOT" inline="true" pathid="openpgp.classpath"/>
> -settingsRef="sign.settingsId"
> +settingsRef="sign.settingsId" log="download-only"
>module="bcprov-jdk16" revision="140" 
> inline="true" pathid="bouncycastle.bcprov.classpath"/>
>
>
> -settingsRef="sign.settingsId" transitive="false"
> +settingsRef="sign.settingsId" transitive="false" log="download-only"
>module="bcpg-jdk15" revision="140" 
> inline="true" pathid="bouncycastle.bcpg.classpath"/>
>
>
>
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [ivy] Ivy 2.0 status

[Maarten Coene]

Yes,

I was working on it untill I got the flue and after that I just didn't find the 
time to continue the work.
But I hope I can finish it this week so we can start the vote.

Maarten




- Original Message 
From: "Scheper, Erik-Berndt" 
To: dev@ant.apache.org
Sent: Tuesday, January 6, 2009 5:37:01 PM
Subject: [ivy] Ivy 2.0 status

Hi,

I was wondering what the status is of ivy 2.0 final. I noticed in fisheye ( 
http://fisheye6.atlassian.com/browse/ant/ivy/core ) that the release was being 
prepared, but haven't heard anything since.

Kind regards,
Erik-Berndt

Disclaimer:
This message contains information that may be privileged or confidential and is 
the property of Sogeti Nederland B.V. or its Group members. It is intended only 
for the person to whom it is addressed. If you are not the intended recipient, 
you are not authorized to read, print, retain, copy, disseminate, distribute, 
or use this message or any part thereof. If you receive this message in error, 
please notify the sender immediately and delete all copies of this message.



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: patch (ivy): log conflict results at verbose

[Maarten Coene]

I'm not convinced that this is the proper way to solve your problem.
If they are not conflicts, they shouldn't get logged as conflict. Could you 
give us more info and an example of your log?

Maarten



- Original Message 
From: Robey Pointer 
To: dev@ant.apache.org
Sent: Friday, January 2, 2009 5:56:07 AM
Subject: patch (ivy): log conflict results at verbose

When ivy is in log="download-only" mode, it will still log potentially dozens 
of lines (in a large project) of "conflicts". They aren't actually conflicts, 
just instances of multiple versions of a package in the cache, so besides being 
noisy, the messages are also a source of confusion/worry.

This patch fixes the log level of these messages so that "conflict" messages 
aren't displayed in quiet mode.

Thanks!
robey


Index: src/java/org/apache/ivy/core/retrieve/RetrieveEngine.java
===
--- src/java/org/apache/ivy/core/retrieve/RetrieveEngine.java(revision 
730653)
+++ src/java/org/apache/ivy/core/retrieve/RetrieveEngine.java(working copy)
@@ -339,7 +339,7 @@
 // which consider as greater a winning artifact
 Collections.sort(artifactsList, getConflictResolvingPolicy());
 // after the sort, the winning artifact is the greatest one, 
i.e. the last one
-Message.info("\tconflict on "
+Message.verbose("\tconflict on "
 + copyDest
 + " in "
 + conflictsConfs


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[VOTE] Ivy 2.0.0 Release

[Maarten Coene]

I have built a release candidate for Ivy 2.0.0

You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.0.0/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~maartenc/m2-staging-repo/

A staging eclipse update site with this release is available here:
http://people.apache.org/~maartenc/updatesite-staging/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Maarten Coene, Ivy 2.0.0 release manager



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: patch (ivy): log conflict results at verbose

[Maarten Coene]

I never saw this message before.
Could you create a JIRA issue and attach the relevant log when running ant in 
verbose mode? That should also tell us which are the conflicting artifacts.

Maarten




- Original Message 
From: Robey Pointer 
To: Ant Developers List 
Sent: Wednesday, January 7, 2009 5:29:01 AM
Subject: Re: patch (ivy): log conflict results at verbose

On 6 Jan 2009, at 12:14, Maarten Coene wrote:

> I'm not convinced that this is the proper way to solve your problem.
> If they are not conflicts, they shouldn't get logged as conflict. Could you 
> give us more info and an example of your log?

I agree, since they aren't conflicts, even the word "conflict" in the message 
is misleading. I just didn't want to change too much -- the real problem is 
that it's logged at info level and can't be quieted. Feel free to change the 
text.

The messages are things like this:

[ivy:retrieve] conflict on 
/Users/robey/code/scala/configgy/target/libs/default/scala-library-2.7.2.jar in 
[default]: 2.7.2 won
[ivy:retrieve] conflict on 
/Users/robey/code/scala/configgy/target/libs/test/scala-compiler-2.7.2.jar in 
[test]: 2.7.2 won
[ivy:retrieve] conflict on 
/Users/robey/code/scala/configgy/target/libs/test/scala-library-2.7.2.jar in 
[test]: 2.7.2 won

I see them in every project I build, at home or at work. Just build a few 
different projects and you will see them. I gather that the real message should 
be something along the lines of "I found jars in your cache and picked the one 
you asked for".

robey


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Ivy 2.0.0 Release

[Maarten Coene]

ok, I'll update the bundle version to "2.0.0.final"

Maarten



- Original Message 
From: Nicolas Lalevée 
To: Ant Developers List 
Sent: Thursday, January 8, 2009 7:51:06 PM
Subject: Re: [VOTE] Ivy 2.0.0 Release

It seems there is an issue with the bundle version of Ivy:
In the generated MANIFEST.MF there is '2.0.0_20090107223116' which is  
an invalid OSGi version.
And to make that final version be considered upper than the RC2, that  
final version cannot be tagged as 2.0.0, because '2.0.0' is considered  
lower than '2.0.0.cr2'. So the bundle version has to be '2.0.0.final'.
I think the release should be rebuild with the correct version.

Nicolas


Le 8 janv. 09 à 00:15, Maarten Coene a écrit :

> I have built a release candidate for Ivy 2.0.0
>
> You can download it from this URL:
> http://people.apache.org/~maartenc/ivy/staging/2.0.0/
>
> A maven 2 staging repo with this release is available here:
> http://people.apache.org/~maartenc/m2-staging-repo/
>
> A staging eclipse update site with this release is available here:
> http://people.apache.org/~maartenc/updatesite-staging/
>
> Do you vote for the release of these binaries?
>
> [ ] Yes
> [ ] No
>
> Regards,
>
> Maarten Coene, Ivy 2.0.0 release manager
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[VOTE] Ivy 2.0.0 Release (2nd attempt)

[Maarten Coene]

I have built a new release candidate for Ivy 2.0.0.
The only difference with the previous attempt is that the Ivy bundle version is 
now "2.0.0.final".

You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.0.0/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~maartenc/m2-staging-repo/

A staging eclipse update site with this release is available here:
http://people.apache.org/~maartenc/updatesite-staging/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Maarten Coene, Ivy 2.0.0 release manager


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Ivy 2.0.0 Release (2nd attempt)

[Maarten Coene]

Since there are only 2 binding votes so far, here is my +1

Maarten




- Original Message 
From: Maarten Coene 
To: ant-dev 
Sent: Thursday, January 8, 2009 11:51:17 PM
Subject: [VOTE] Ivy 2.0.0 Release (2nd attempt)

I have built a new release candidate for Ivy 2.0.0.
The only difference with the previous attempt is that the Ivy bundle version is 
now "2.0.0.final".

You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.0.0/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~maartenc/m2-staging-repo/

A staging eclipse update site with this release is available here:
http://people.apache.org/~maartenc/updatesite-staging/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Maarten Coene, Ivy 2.0.0 release manager


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[RESULT][VOTE] Ivy 2.0.0 Release (2nd attempt)

[Maarten Coene]

The vote has ended for the Ivy 2.0.0 release.

With 3 binding +1 and no vetoes, the release is accepted.
I'll finish the release process within the next couple of days.

Maarten



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[DISCUSS]Ivy 2.0.0 announcement text

[Maarten Coene]

Hi,

I prepared the announcement text for the 2.0.0 release of Ivy (see below).
Please post your feedback quickly, I would like to announce it on monday or 
tuesday.

Maarten

==
 - The Ivy project is pleased to announce its
2.0.0 release.

Ivy is a tool for managing (recording, tracking, resolving and
reporting) project dependencies, characterized by flexibility,
configurability, and tight integration with Apache Ant.

Key features of the 2.0.0 release are
* enhanced Maven2 compatibility, with several bug fixes and more
  pom features covered
* improved cache management, including dynamic revision caching
  with fine grain TTL
* improved concurrency support with cache locking and atomic publish
* namespace aware validation, allowing to use validation with
  extra attributes
* better and more homogeneous relative paths handling
* better support for local builds
* numerous bug fixes as documented in Jira and in the release notes

We encourage all users of Ivy to update to this new version.

Issues should be reported to:
https://issues.apache.org/jira/browse/IVY

Download the 2.0.0 release at:
http://ant.apache.org/ivy/download.cgi

More information can be found on the Ivy website:
http://ant.apache.org/ivy/

Regards,
Maarten Coene
==



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [ivy] javascript syntax error upon loading ivy home page

[Maarten Coene]

It's not a synchronization problem, I think I did something wrong uploading the 
site, but I don't know how to fix it (yet)...

Maarten



- Original Message 
From: "Scheper, Erik-Berndt" 
To: dev@ant.apache.org
Sent: Thursday, January 22, 2009 8:26:34 AM
Subject: [ivy] javascript syntax error upon loading ivy home page

Hi,

When I load the ivy home page (http://ant.apache.org/ivy) I get a syntax error, 
both in Mozilla Firefox and Internet Explorer. 

Error whie executing script from URL http://ant.apache.org/ivy/config.extra.js: 
SyntaxError: syntax error.

This may be a synchronization problem due to deployment of ivy 2.0

Regards,

Erik-Berndt

Disclaimer:
This message contains information that may be privileged or confidential and is 
the property of Sogeti Nederland B.V. or its Group members. It is intended only 
for the person to whom it is addressed. If you are not the intended recipient, 
you are not authorized to read, print, retain, copy, disseminate, distribute, 
or use this message or any part thereof. If you receive this message in error, 
please notify the sender immediately and delete all copies of this message.



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[ANNOUNCE] Ivy 2.0.0 released

[Maarten Coene]

The Ivy project is pleased to announce its 2.0.0 release.
This is the first non-beta release of Ivy under Apache.

Ivy is a tool for managing (recording, tracking, resolving and
reporting) project dependencies, characterized by flexibility,
configurability, and tight integration with Apache Ant.

Key features of the 2.0.0 release are
* enhanced Maven2 compatibility, with several bug fixes and more
  pom features covered
* improved cache management, including dynamic revision caching
  with fine grain TTL
* improved concurrency support with cache locking and atomic publish
* namespace aware validation, allowing to use validation with
  extra attributes
* new 'packager' resolver added
* better and more homogeneous relative paths handling
* better support for local builds
* numerous bug fixes as documented in Jira and in the release notes

We encourage all users of Ivy to update to this new version.

Issues should be reported to:
https://issues.apache.org/jira/browse/IVY

Download the 2.0.0 release at:
http://ant.apache.org/ivy/download.cgi

More information can be found on the Ivy website:
http://ant.apache.org/ivy/

Regards,
Maarten Coene


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [ivy] javascript syntax error upon loading ivy home page

[Maarten Coene]

The site should be ok now

Maarten



- Original Message 
From: "Scheper, Erik-Berndt" 
To: dev@ant.apache.org
Sent: Thursday, January 22, 2009 8:26:34 AM
Subject: [ivy] javascript syntax error upon loading ivy home page

Hi,

When I load the ivy home page (http://ant.apache.org/ivy) I get a syntax error, 
both in Mozilla Firefox and Internet Explorer. 

Error whie executing script from URL http://ant.apache.org/ivy/config.extra.js: 
SyntaxError: syntax error.

This may be a synchronization problem due to deployment of ivy 2.0

Regards,

Erik-Berndt

Disclaimer:
This message contains information that may be privileged or confidential and is 
the property of Sogeti Nederland B.V. or its Group members. It is intended only 
for the person to whom it is addressed. If you are not the intended recipient, 
you are not authorized to read, print, retain, copy, disseminate, distribute, 
or use this message or any part thereof. If you receive this message in error, 
please notify the sender immediately and delete all copies of this message.



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Announcing Ivy 2.0.0 release on Ant homepage

[Maarten Coene]

How do I mention the Ivy 2.0.0 release on the ant homepage?
I guess I have to add it to 
http://svn.apache.org/repos/asf/ant/core/trunk/xdocs/antnews.xml ?

But what do I have to do next?

Maarten



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: AW: Announcing Ivy 2.0.0 release on Ant homepage

[Maarten Coene]

I've updated the announcement.

Thanks to your instructions :-)
(although the Jakarta site part didn't work for me, I had do download velocity)

Maarten




- Original Message 
From: "jan.mate...@rzf.fin-nrw.de" 
To: dev@ant.apache.org
Sent: Friday, January 23, 2009 10:30:50 AM
Subject: AW: Announcing Ivy 2.0.0 release on Ant homepage

1. update on the local svn copy ;)
2. update the antnews.xml
   a) not sure about updating the s
   b) add a new  as (new) first in the  similar to the other
3. regenerate the site
   - Use Ant for generation
 ant -f docs.xml -Dsite.dir=%JAKARTA_SITE%
   - You need Anakia for that. On See 
http://jakarta.apache.org/site/jakarta-site2.html
4. check in the antnews.xml and antnews.html
5. wait until the jobs have picked up the modifications and published them ...


Jan

p.s.
I prepared the initial announcement, but you want to add more I think ;)

>-Ursprüngliche Nachricht-----
>Von: Maarten Coene [mailto:maarten_co...@yahoo.com] 
>Gesendet: Freitag, 23. Januar 2009 00:08
>An: ant-dev
>Betreff: Announcing Ivy 2.0.0 release on Ant homepage
>
>How do I mention the Ivy 2.0.0 release on the ant homepage?
>I guess I have to add it to 
>http://svn.apache.org/repos/asf/ant/core/trunk/xdocs/antnews.xml ?
>
>But what do I have to do next?
>
>Maarten
>
>
>
>  
>
>-
>To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
>For additional commands, e-mail: dev-h...@ant.apache.org
>
>

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Should I open a vote ? (Re: svn commit: r740252 - in /ant/ivy/updatesite/trunk/dist: ./ features/ plugins/)

[Maarten Coene]

I'm fine with your change, I don't think you need a vote for it.

Maarten




- Original Message 
From: Nicolas Lalevée 
To: Ant Developers List 
Sent: Monday, February 9, 2009 6:41:13 PM
Subject: Should I open a vote ? (Re: svn commit: r740252 - in 
/ant/ivy/updatesite/trunk/dist: ./ features/ plugins/)

So, does anybody have any hint on this ?

Nicolas

On mardi 03 février 2009 10:26:57 Nicolas Lalevée wrote:
> To fix IVYDE-156 [1], I had to change some deployed artifacts. For the Ivy
> jar itself, a 'svn move' was sufficent. But for the Ivy feature jar
> (Eclipse packaging around the Ivy jar) and the digest.zip (a compressed
> metadata descriptor of the plugins in the updatesite), I had to rebuild
> them, put new checksum, and resign them.
>
> So do I need to launch a vote for this Eclipse-packaging-fix release ?
>
> Nicolas
>
> [1] https://issues.apache.org/jira/browse/IVYDE-156
>
> On mardi 03 février 2009 10:17:32 hi...@apache.org wrote:
> > Author: hibou
> > Date: Tue Feb  3 09:17:30 2009
> > New Revision: 740252
> >
> > URL: http://svn.apache.org/viewvc?rev=740252&view=rev
> > Log:
> > IVYDE-156: fix the current update site so that versions match
> >
> > Added:
> >
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >_2 0090108225011.jar   (with props)
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >_2 0090108225011.jar.asc
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >_2 0090108225011.jar.md5
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >_2 0090108225011.jar.sha
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar   (props changed) - copied unchanged from r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar.asc   (props changed) - copied unchanged from r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.asc
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar.md5   (props changed) - copied unchanged from r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.md5
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar.pack.gz   (contents, props changed) - copied, changed from
> > r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar.pack.gz.asc   (contents, props changed) - copied, changed from
> > r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z.asc
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar.pack.gz.md5   (contents, props changed) - copied, changed from
> > r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z.md5
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar.pack.gz.sha   (contents, props changed) - copied, changed from
> > r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z.sha
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final_20090108
> >22 5011.jar.sha   (props changed) - copied unchanged from r739941,
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.sha
> > Removed:
> >
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >.j ar
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >.j ar.asc
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >.j ar.md5
> > ant/ivy/updatesite/trunk/dist/features/org.apache.ivy.feature_2.0.0.final
> >.j ar.sha
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.asc
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.md5
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z.asc
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z.md5
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.pack
> >.g z.sha
> > ant/ivy/updatesite/trunk/dist/plugins/org.apache.ivy_2.0.0.final.jar.sha
> > Modified:
> > ant/ivy/updatesite/trunk/dist/digest.zip
> > ant/ivy/updatesite/trunk/dist/digest.zip.asc
> > ant/ivy/updatesite/trunk/dist/digest.zip.md5
> > ant/ivy/updatesite/trunk/dist/digest.zip.sha
> > ant/ivy/updatesite/trunk/dist/site.xml
> >
> > Modified: ant/ivy/updatesite/trunk/dist/digest.zip
> > URL:
> > http://svn.apache.org/viewvc/ant/ivy/updatesite/trunk/dist/digest.

Re: [Ivy] webdav support

[Maarten Coene]

I don't know about vfs, but Ivy doesn't fail any longer if you have 
httpclient-2.x in your classpath.
In that situation, Ivy will use the default JDK URL classes...

Maarten




- Original Message 
From: Hans Dockter 
To: Ant Developers List 
Sent: Wednesday, February 11, 2009 8:24:30 PM
Subject: Re: [Ivy] webdav support

One problem with the webdav support of vfs was that that they were using an old 
version of commons-httpclient, which was incompatible to the version which is 
Ivy using for other purposes. It would be interesting to know if this is still 
an issue with the new webdav implementation of vfs.

- Hans

On Feb 11, 2009, at 8:56 AM, Xavier Hanin wrote:

> Webdav support is often requested in Ivy, so I think it would be a
> good idea to test this indeed.
> 
> Xavier
> 
> On Tue, Feb 10, 2009 at 10:53 PM, Matt Benson  wrote:
>> 
>> Actually, I've been meaning to poke the dev list on this one.  Ralph Goers 
>> has recently added to Commons VFS trunk a new webdav implementation, based 
>> on Jackrabbit DAV instead of Slide.  It should be a priority (albeit perhaps 
>> a minor one) to test a trunk build of [vfs] to see if everything works as 
>> expected.
>> 
>> Regards,
>> Matt
>> 
>> 
>> --- On Tue, 2/10/09, Mandie Smith  wrote:
>> 
>>> From: Mandie Smith 
>>> Subject: webdav support
>>> To: ivy-u...@ant.apache.org
>>> Date: Tuesday, February 10, 2009, 3:43 PM
>>> I've been looking through the archives, and the last
>>> mention about webdav
>>> support I've seen was March of last year.  I was
>>> wondering if anyone has
>>> looked into this and what their progress was?
>>> 
>>> thanks,
>>> Mandie
>> 
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
>> For additional commands, e-mail: dev-h...@ant.apache.org
>> 
>> 
> 
> 
> 
> --Xavier Hanin - 4SH France
> BordeauxJUG co leader - http://www.bordeauxjug.org/
> Blogger - http://xhab.blogspot.com/
> Apache Ivy Creator - http://ant.apache.org/ivy/
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
> 

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Should I open a vote ? (Re: svn commit: r740252 - in /ant/ivy/updatesite/trunk/dist: ./ features/ plugins/)

[Maarten Coene]

Creating a 2.0.1 release is ok for me. I'm willing to create the release if 
no-one else volunteers...

I've taken a quick look at the changes in JIRA, I think IVY-970 contains the 
biggest change, but I think we can include it in the new release (or is it too 
risky?)
And maybe we should also try to fix IVY-987 in the 2.0.1 release to improve our 
maven2 compatibility?

Maarten





- Original Message 
From: Xavier Hanin 
To: Ant Developers List 
Sent: Wednesday, February 11, 2009 8:53:20 AM
Subject: Re: Should I open a vote ? (Re: svn commit: r740252 - in  
/ant/ivy/updatesite/trunk/dist: ./ features/ plugins/)

On Tue, Feb 10, 2009 at 9:04 AM, Stefan Bodewig  wrote:
> On 2009-02-10, Xavier Hanin  wrote:
>
>> On Tue, Feb 10, 2009 at 5:31 AM, Stefan Bodewig  wrote:
>>> On 2009-02-09, Nicolas Lalevée  wrote:
>
> So do I need to launch a vote for this Eclipse-packaging-fix release ?
>
>>> I'd create a minor version release (2.0.1 or even just 2.0.0.1) - and
>>> vote as on any release.
>> A minor version release of what? Ivy? IvyDE?
>
> Whatever it is that needs its packaging to be changed.
Well, in this case we need a new packaging of Ivy eclipse feature,
which is packaged when we release Ivy, so I guess we need to release
Ivy itself. And if we release a new minor version of Ivy, I think
people would be confused if we do not include some bug fixes which are
currently on trunk. So I think it's a good opportunity to release Ivy
2.0.1, and discuss what we put in this release (what we merge from
trunk to 2.0.x branch).

WDYT?

Xavier
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>



-- 
Xavier Hanin - 4SH France
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

changing Ivy retrieve behaviour

[Maarten Coene]

Hi,

I would like to change the Ivy retrieve behaviour regarding conflict handling 
when multiple artifacts are retrieved to the same file.
At the moment, Ivy has some kind of retrieve-conflict-manager which selects the 
"best" artifact, based on the revision of the conflicting modules.
This doesn't work when multiple artifacts of the same module is retrieved to 
the same file. At the moment, this is causing problems with the maven 
source/javadoc artifacts which are sometimes retrieved instead of the 
class-files.

I would like to change this so that Ivy throws an error if multiple different 
artifacts map to the same file.
Any objections?

Maarten



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: changing Ivy retrieve behaviour

[Maarten Coene]

If we make it possible to selet the retrieve conflict strategy, would it be ok 
to make the "fail"-strategy the default one?

Or maybe we could adapt the current conflict strategy to only to select the 
latest version of the same artifact (same name, type, extension, extra 
attributes) and throw an error in any other situation.
In this situation, retrieving the source and classes artifacts of the same 
module to the same file will result in an error while retrieving the classes 
artifacts of version 1.0 and 1.1 of the same module will result in the current 
behaviour.

This way, we are more or less backwards compatible, and we'll solve a very 
common problem

Maarten




- Original Message 
From: Xavier Hanin 
To: Ant Developers List 
Sent: Tuesday, March 10, 2009 5:06:43 PM
Subject: Re: changing Ivy retrieve behaviour

On Mon, Mar 9, 2009 at 6:53 PM, Gilles Scokart  wrote:

> I think failing the build is indeed the best aproach.  But I fear some
> build
> that might be broken.  Isn't it?

I think some builds would fail, so I'd classify this as non backward
compatible change. So I think the best would be to be able to select the
retrieve conflict management strategy, or at least to have the option to use
the current behaviour (simple messages) when needed.

Xavier


>
> I'm also wondering if it is not possible to have warning in the retrieve
> task when some kind of patterns are used.
>
> Gilles Scokart
>
>
> 2009/3/9 Maarten Coene 
>
> >
> > Hi,
> >
> > I would like to change the Ivy retrieve behaviour regarding conflict
> > handling when multiple artifacts are retrieved to the same file.
> > At the moment, Ivy has some kind of retrieve-conflict-manager which
> selects
> > the "best" artifact, based on the revision of the conflicting modules.
> > This doesn't work when multiple artifacts of the same module is retrieved
> > to the same file. At the moment, this is causing problems with the maven
> > source/javadoc artifacts which are sometimes retrieved instead of the
> > class-files.
> >
> > I would like to change this so that Ivy throws an error if multiple
> > different artifacts map to the same file.
> > Any objections?
> >
> > Maarten
> >
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> > For additional commands, e-mail: dev-h...@ant.apache.org
> >
> >
>



-- 
Xavier Hanin - 4SH France
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: changing Ivy retrieve behaviour

[Maarten Coene]

I've updated the RetrieveEngine to throw an error if multiple artifacts of the 
same module are mapped to the same filename.
The behaviour when multiple artifacts of different modules are mapped to the 
same filename hasn't been changed.

Could you review this change and are you ok to include that in a 2.0.1 release?
If so, I'll start with preparing the 2.0.1 release, unless someone else want to 
make the 2.0.1 release.

Maarten




- Original Message 
From: Xavier Hanin 
To: Ant Developers List 
Sent: Thursday, March 12, 2009 12:00:19 PM
Subject: Re: changing Ivy retrieve behaviour

> Or maybe we could adapt the current conflict strategy to only to select the
> latest version of the same artifact (same name, type, extension, extra
> attributes) and throw an error in any other situation.

That sounds good indeed, and I agree in this case it could be considered
more or less as a bug fix rather than a real change  in behaviour. So in
this case I'd even be ok to put it in a 2.0.x release.

Xavier


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

New Ivy release

[Maarten Coene]

Hi all,

it's time to make a new Ivy release.
I volunteer to be release manager, but we should discuss the following first:

- what will be the new Ivy version: 2.0.1 or 2.1.0 
- what changes will we include in this new release?
- will we create a release candidate first?

My answers to these questions are:
- new version: I'd prefer 2.1.0, but I'm ok with 2.0.1 as well
- what changes: everything that has been committed to trunk
- release candidate: yes

regards,
Maarten



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: New Ivy release

[Maarten Coene]

Thanks all for the feedback. I've created a 2.1.0-rc1 version of Ivy containing 
all changes from trunk.
I'll post the vote to this list in a few minutes...

Maarten




- Original Message 
From: Gilles Scokart 
To: Ant Developers List 
Sent: Wednesday, March 18, 2009 8:54:55 PM
Subject: Re: New Ivy release

Gilles Scokart


2009/3/17 Maarten Coene 

>
> Hi all,
>
> it's time to make a new Ivy release.
> I volunteer to be release manager, but we should discuss the following
> first:



Cool, thanks,


>
>
> - what will be the new Ivy version: 2.0.1 or 2.1.0
> - what changes will we include in this new release?


I would rather ask : what not include ?

>
> - will we create a release candidate first?
>

I don't think it is required.  Maybe we can have a longer period to validate
the jar to release so that we can make some tests with it.


> My answers to these questions are:
> - new version: I'd prefer 2.1.0, but I'm ok with 2.0.1 as well
> - what changes: everything that has been committed to trunk
> - release candidate: yes
>
> regards,
> Maarten
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[VOTE] Ivy 2.1.0-rc1 Release

[Maarten Coene]

I have built Ivy 2.1.0-rc1

You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.1.0-rc1/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~maartenc/m2-staging-repo/

A staging eclipse update site with this release is available here:
http://people.apache.org/~maartenc/updatesite-staging/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Maarten Coene, 
Ivy 2.1.0-rc1 release manager 



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Ivy 2.1.0-rc1 Release

[Maarten Coene]

FYI, the release notes and changes of this release can be seen here:
https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.1.x/RELEASE_NOTES

These release notes are also included in the binaries...

Maarten




- Original Message 
From: Maarten Coene 
To: ant-dev 
Sent: Thursday, March 19, 2009 10:51:57 PM
Subject: [VOTE] Ivy 2.1.0-rc1 Release


I have built Ivy 2.1.0-rc1

You can download it from this URL:
http://people.apache.org/~maartenc/ivy/staging/2.1.0-rc1/

A maven 2 staging repo with this release is available here:
http://people.apache.org/~maartenc/m2-staging-repo/

A staging eclipse update site with this release is available here:
http://people.apache.org/~maartenc/updatesite-staging/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

Maarten Coene, 
Ivy 2.1.0-rc1 release manager 



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[RESULT][VOTE]Ivy 2.1.0-rc1 Release

[Maarten Coene]

Hi all,

With 4 binding +1 and 1 non binding, I'm pleased to announce that this vote has 
passed successfully.
I'll continue with the release process within the next couple of days.

Maarten



  

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org