> -----Original Message----- > From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED] > Sent: donderdag 28 september 2000 8:50 > To: '[EMAIL PROTECTED]' > Subject: RE: New inner element for <java> > > > > From: Barrie Treloar [mailto:[EMAIL PROTECTED] > > > > On Wed, 27 Sep 2000, Jose Alberto Fernandez wrote: > > > > > Hi, > > > > > > I find myself in need of yet another feature for the <java> > > task. I would > > > appreciate any input you can provide on the utility or best > > way to do it. > > > > > > I would like to add a <property name="..." value="..."> element that > > > depending on whether the VM is forked or not will generate > > "-Dname=value" > > > arguments or it will manipulate the System.properties. > > > > > > the syntax of the element will be: > > > > > > <property name="a" value="x" /> or <property name="b" > > file="a file name" /> > > > > > > one of the important reasons for this is my need to > > indicate file names on > > > this parameters. > > > > > > Do you think the name is problematic? How about<propertyArg>? > > > > Aren't these vm arguments. Can you use <vmargs> to include them, the > > documentation indicates its only used if the java task forks. > > > > Yes and no. -D options are vm arguments, but they would be > ignored if the VM > is not forked. I want to be able to use them even when no forking occurs. > > Jose Alberto >
Funny this comes up at the very moment that I need it too. I thought that ant already put all of its properties in the System.properties because then you wouldn't need this extra argument to <java>. But since it doesn't, I like this solution. I'm willing to do some coding here, but are there any classes in eg. the types package that I could use. I'm not so familiar with the latest changes to ant. Marcel Schutte
