RE: -propertyfile ant switch

> -Original Message- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: quinta-feira, 19 de Janeiro de 2006 5:10 > To: user@ant.apache.org > Subject: Re: -propertyfile ant switch > > On Wed, 18 Jan 2006, Paulo Jorge Guedes <[EMAIL PROTECTED]> > wrote:

-propertyfile ant switch

Hi, I use "inheritAll=false" so I have to use the -propertyfile switch to have properties available to all projects. The problem is that I call ant from CruiseControl and I can't use this switch. I tried to use the "propertyfile" target but it didn't work. Do you know any other solution? Paulo

RE: macrodef

> -Original Message- > From: Alexey N. Solofnenko [mailto:[EMAIL PROTECTED] > Sent: terça-feira, 17 de Janeiro de 2006 19:21 > To: Ant Users List > Subject: Re: macrodef > > Well, you can do it via internal ANT API, but it would be a too complex > solution for the task. Yeah... I'll overr

RE: macrodef

nsert necessary elements into that copy. But I have to rewrite all the macrodef settings, i.e., there isn't a way to just add more settings to the already defined macrodef? Paulo > - Alexey. > > Paulo Jorge Guedes wrote: > > Hi, > > > > I have a target (-init-ma

macrodef

Hi, I have a target (-init-macrodef-junit ) that initializes "junit" target using the "macrodef" element. It doesn't declare the "formatter" element and I need to have the reports printed. The thing is I can't touch that file. Is there any way to "append" the "formatter" child element to the juni

RE: Relative paths

> -Original Message- > From: Clifton Craig [mailto:[EMAIL PROTECTED] > Sent: sexta-feira, 13 de Janeiro de 2006 14:04 > To: Ant Users List > Subject: Re: Relative paths > > > One more suggestion, maybe you could clean it up a little by using: > > Thanks for all th

RE: Relative paths

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: sexta-feira, 13 de Janeiro de 2006 13:20 > To: Ant Users List > Subject: RE: Relative paths > > >It looks on the nbproject path... > > I thought, that is what you want. > That's nice, I don't understand your

RE: Relative paths

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: sexta-feira, 13 de Janeiro de 2006 12:38 > To: Ant Users List > Subject: RE: Relative paths > > OK, > inheritall="false" > is better than using the dir attribute. And the dir attribute doesn't work :) It look

RE: Relative paths

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: sexta-feira, 13 de Janeiro de 2006 11:57 > To: Ant Users List > Subject: RE: Relative paths > > Something like this maybe help you in your root build.xml: > > > inheritall="true" inheritrefs="tr

RE: Relative paths

Original Message- > From: Paulo Jorge Guedes [mailto:[EMAIL PROTECTED] > Sent: sexta-feira, 13 de Janeiro de 2006 10:49 > To: Ant Users List > Subject: Relative paths > > Hi, > > I have this directory structure: > > Root > Apps >

Relative paths

Hi, I have this directory structure: Root Apps App1 Nbproject Src The build.xml files just import the files in the inner directories. The build file on nbproject folder does all the work. In each file I set the "basedir" att

RE: Classpath

> run ant with -lib j2ee.jar to have it stuck on Ant's classpath. It worked, thanks a lot! Paulo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Classpath

Hi, I created an enterprise project with NetBeans and I need to build it with ant, from the command line. I'm having a problem with the classpath. I need to import javax.ejb.* but it won't find the proper jar (j2ee.jar). The only way I can make ant to find it is setting the attribute "classpathref