Re: Merging rev 628990 to the 1.7.x branch

Hi Stefan, > Is it OK if I merge > into the 1.7.x > branch before we release 1.7.1 (maybe even before Kev creates the RC > build, but I'd like to have his opinion here first). I've been following the discussion and was waiting until a patch/

Merging rev 628990 to the 1.7.x branch

Hi all (especially Kev 8-) Is it OK if I merge into the 1.7.x branch before we release 1.7.1 (maybe even before Kev creates the RC build, but I'd like to have his opinion here first). Currently Cactus users are forced to stick with 1.6.5 sin

Re: The Cactus/JUnit-Task problem

On Tue, 19 Feb 2008, Petar Tahchiev <[EMAIL PROTECTED]> wrote: > Once again sorry, and you can feel free to apply the patch to > Ant 1.7.2 and Ant 1.8. It already is in trunk, so it should go into 1.8. I'll see whether it can go into 1.7.1. Stefan --

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

Re: svn commit: r629230 - in /ant/ivy/core/trunk: src/java/org/apache/ivy/plugins/parser/m2/ test/java/org/apache/ivy/plugins/parser/m2/

On Feb 19, 2008 10:03 PM, <[EMAIL PROTECTED]> wrote: > Author: gscokart > Date: Tue Feb 19 13:03:21 2008 > New Revision: 629230 > > URL: http://svn.apache.org/viewvc?rev=629230&view=rev > Log: > IVY-637 m2 incompatibility - IVY does not recognize property section > (partial fix, the case of proper

Re: [jira] Resolved: (IVY-683) M2 parent pom dependencies are not added

Gilles, I've quickly reviewed your last commits, sounds like an amazing job! This is a huge improvement to pom parsing, you have my kudos! So now we should be able to make the beta 2 release. We just need to apply Adrian patch before (provided on IVY-399). I'm afraid I won't have time before thur

Re: The Cactus/JUnit-Task problem

Hi everybody, I am really, really sorry for my ignorance :-(. I spent the whole day, trying to figure out what is the reason for the vmCrashString to be null. And I found it, actually :-). The reason was me :-). I unintentially was adding the to the classpath. After removing it, everyth