Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Subject: Re: [logging] Re: svn commit: r383771 -
	/jakarta/commons/proper/logging/contrib/simon/jcl2/build.xml
From: Simon Kitching <skitching@apache.org>
Reply-To: skitching@apache.org
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
In-Reply-To: <1141762543.5148.4.camel@knossos.elmet>
References: <20060307041735.61654.qmail@minotaur.apache.org>
	 <440DBC4E.7040808@btopenworld.com>  <1141762543.5148.4.camel@knossos.elmet>
Content-Type: text/plain
Date: Wed, 08 Mar 2006 15:09:29 +1300
Message-Id: <1141783769.4631.34.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2006-03-07 at 20:15 +0000, robert burrell donkin wrote:
> On Tue, 2006-03-07 at 17:01 +0000, Stephen Colebourne wrote:
> > Er, I think I would have to -1 a release without an ant build, so I'm 
> > hoping this is temporary :-)
> 
> AIUI simon's working in contrib on some ideas for JCL2. the work on the
> (much delayed) JCL 1.1 release is happening on trunk.

Yep, as Robert says this removal of the ant build.xml was only for my
experimental code.

It was removed mainly because it is currently broken and as the mvn2
build works I can't be bothered fixing it right now. However I
personally don't see any reason why we would want an ant buildfile for
JCL2 if the maven one works fine (and it uses the appropriate JDKs to do
the actual compile and test steps).

Cheers,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org