IVY SVN duplicated under Ant and Incubator SVN

2010-06-11 Thread sebb
Ivy started out as an Incubator project with code in: http://svn.apache.org/repos/asf/incubator/ivy/ It is now an Ant sub-project with code in: http://svn.apache.org/repos/asf/ant/ivy/ However the incubator SVN tree still has files in it Something seems to have gone wrong here. --

Re: Hudson target to build Ant via Maven

2010-06-11 Thread Antoine Levy-Lambert
Jesse Glick wrote: > There appears to be a Hudson server which builds Ant periodically > using bootstrap.sh, I presume. (I cannot access the server even to > look at it, much less configure it.) > > Shouldn't there be an analogous job which runs Maven on > src/etc/pom.xml? The POMs are tricky to ma

Hudson target to build Ant via Maven

2010-06-11 Thread Jesse Glick
There appears to be a Hudson server which builds Ant periodically using bootstrap.sh, I presume. (I cannot access the server even to look at it, much less configure it.) Shouldn't there be an analogous job which runs Maven on src/etc/pom.xml? The POMs are tricky to maintain - well, actually eas

Re: [DISCUSS] Commercial Tasks in Ant

2010-06-11 Thread Bruce Atherton
On 01/06/2010 7:51 AM, Stefan Bodewig wrote: On 2010-05-29, Bruce Atherton wrote: I'd like to discuss whether to move all of the commercial tasks out of Ant core/optional libraries and putting them each into their own Antlibs. +1 - I'm not sure we must stop at the commercial task (is

Re: Ivy 2.2.0-RC1

2010-06-11 Thread Maarten Coene
Very strange indeed. I just tried it myself with IvyDE and default settings and I didn't had any problem... Are you behind a proxy? Maarten - Original Message From: Jon Stevens To: Ant Developers List Sent: Fri, June 11, 2010 6:19:43 PM Subject: Re: Ivy 2.2.0-RC1 I was trying it w

Re: Ivy 2.2.0-RC1

2010-06-11 Thread Jon Stevens
I was trying it with the Ivy Eclipse Plugin and it wasn't working at all. The error was that it couldn't find the jar files in the maven repository. jon On Thu, Jun 10, 2010 at 2:12 PM, Maarten Coene wrote: > Yeah, writing good documentation can be very difficult and time consuming. > Patches ar