AW: Ruby on Rails ahead when it comes to unified build and deploy

>The Ruby on Rails world seems to have it covered when it comes >to unifying >build through deployment using a consistent tool chain. > >* rake for build >* capistrano for deploy >** cap is based on rake > >Aligning tools like this is a good idea enabling tighter >application life >cycle time an

Re: Branch Management

Branching is not a first-class concept in the ivy world, that I know if. Is there an integration with your revision control that you're trying out? Here we just don't branch the ivy repository, that seems to be common because the binary artifacts shouldn't change. On Tue, 2009-04-07 at 12:12 +010

Ruby on Rails ahead when it comes to unified build and deploy

The Ruby on Rails world seems to have it covered when it comes to unifying build through deployment using a consistent tool chain. * rake for build * capistrano for deploy ** cap is based on rake Aligning tools like this is a good idea enabling tighter application life cycle time and leverages

Re: Increasing the memory!

Le Tuesday 07 April 2009 14:54:20 S G, vous avez écrit : > Hi, >     How to increase the memory while running the ant task.I am getting > OutOfMemoryError.I am not using javac task,for which i know how to > increase. Thanks for the help. export ANT_OPTS="-Xmx $ANT_OPTS" -- Francis Galiegue f...@

Re: AW: classpath problem when creating a jar

On Tuesday 7 April 2009 14:55:33 Martin Gainty's cat walking on the keyboard wrote: > what does the jar's manifest display? Here it is: Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 10.0-b23 (Sun Microsystems Inc.) Built-By: luca Main-Class: g2.main.Main Class-Path: aspectjrt.j

RE: AW: classpath problem when creating a jar

what does the jar's manifest display? Martin __ Verzicht und Vertraulichkeitanmerkung Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder F

Increasing the memory!

Hi,     How to increase the memory while running the ant task.I am getting OutOfMemoryError.I am not using javac task,for which i know how to increase.    Thanks for the help.

Re: AW: classpath problem when creating a jar

On Tuesday 7 April 2009 13:43:41 jan.mate...@rzf.fin-nrw.de's cat walking on the keyboard wrote: > So you got a directory layout with > > .../ > >| app.jar {Class-Path: ./conf } > >+-- conf > *.properties Yes, that's the final layout. But I don't get why it is not working. Luca

AW: classpath problem when creating a jar

>I've got my source tree that includes a conf directory with different >configuration files, including a resource bundle properties file. >Now in the jar task of my build file I've got the following entry: > > > >and before that I have a task that copies the conf directory >in the deployment dir

classpath problem when creating a jar

Hi all, I've got my source tree that includes a conf directory with different configuration files, including a resource bundle properties file. Now in the jar task of my build file I've got the following entry: and before that I have a task that copies the conf directory in the deployment dir

File handles aren't closed/released when using Junit task in Ant

I've been using the Junit task, both with "fork=yes" and w/o it. In both cases, some files which are created & written to as part of the Junit tests which the task runs, appear as still open by the java process when the whole Ant build is finished . and so the next build which starts by attempt