Re: Composite Properties

Not easily. The way I've done it in the past is: 1) echo "$name.jar.path" to a temp file. 2) use loadfile with an ExpandProperties filter on it to load the contents of the file into a variable. This variable will contain the value of the expression you want 3) delete the temp file. 4) use the

RE: How do I install Ant?

Why do you need any installation? Just unzip and it will work. You might want to specify ANT_HOME environment variable. - Alexey. -- { http://trelony.cjb.net/ } Alexey N. Solofnenko { http://www.inventigo.com/ } Inventigo LLC Pleasant Hill, CA (GMT-8 usually) -Original Message- From:

How do I install Ant?

Hello, I downloaded the zip file but now want to install Ant. Can someone please let me know how? Anand

Composite Properties

Is there anyway to specify a composite property? For example: "${ ${name} .jar.path}" -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: RE: $ problem in ANT task...

Looks like you're right. I couldn't find a clear note about the $ business in the docs quickly, not even in the 'Using Ant> Properties' section. I must have missed it... --DD -Original Message- From: Nicklas McCalip [mailto:NEMcCalip@;bcbsms.com] Sent: Friday, November 15, 2002 2:31 PM To

Fwd: RE: $ problem in ANT task...

It was version 1.5 and the behavior you described is exactly what I found. I had searched the archives and found nothing mentioning it so wasn't sure it was common knowledge. I see that it is now. Thanks fot the response, Nick --- TEXT.htm follows --- It wa

RE: $ problem in ANT task...

Which version of Ant? Before 1.4, Ant required doubling the $ signs. So $$ resulted in $, etc... This still is the case in 1.5+ (for backward compatibility), but now $ sign on there own (not followed by a {, as in '${prop}') are left alone. So 'abc$def' stays as 'abc$def', while 'abc$$def' is comp

RE: $ problem in ANT task...

I think this is the default behaviour. If you want to display a string character ($), you have to escape it or place a string character before it ($$). d. -Original Message- From: Nicklas McCalip [mailto:NEMcCalip@;bcbsms.com] Sent: Friday, November 15, 2002 3:05 PM To: [EMAIL PROTECTED]

Re: Re[2]: JBoss 2.4.x taskdef

On Friday 15 November 2002 10:10, Jacob Kjome wrote: > I believe that XDoclet auto-generates the Home and Remote interfaces > *and* creates the deployment descriptors. All this is done using > Javadoc statments. In fact, XDoclet is just a Doclet for Javadoc. > > JBoss provides free documentation

$ problem in ANT task...

I came across something the other day that I thought someone might want to take a look at. I was setting up a custom JDBCTask and was having problems getting a conncetion to the database. It wasn't until I echoed my userid and password that I realized what it was. You see the password we use

Re: Re[2]: JBoss 2.4.x taskdef

On Friday 15 November 2002 10:10, Jacob Kjome wrote: > I believe that XDoclet auto-generates the Home and Remote interfaces > *and* creates the deployment descriptors. All this is done using > Javadoc statments. In fact, XDoclet is just a Doclet for Javadoc. > > JBoss provides free documentation

Re: JBoss 2.4.x taskdef

On 2002.11.15 12:26:06 -0500 Daniel Bruce Lynes wrote: > On Friday 15 November 2002 08:36, David Jencks wrote: > > > I can't figure out what this task does and how it differs from xdoclet. > > What does xdoclet do? One of the many things xdoclet does is generate ejb home and remote interfaces, e

RE: Re[2]: JBoss 2.4.x taskdef

If I read Erik correctly, this is no longer true for the latest version of XDoclet, which was supposed to be near a release. --DD -Original Message- From: Jacob Kjome [mailto:hoju@;visi.com] Sent: Friday, November 15, 2002 12:10 PM To: Ant Users List Subject: Re[2]: JBoss 2.4.x taskdef I

Re[2]: JBoss 2.4.x taskdef

Hello Daniel, I believe that XDoclet auto-generates the Home and Remote interfaces *and* creates the deployment descriptors. All this is done using Javadoc statments. In fact, XDoclet is just a Doclet for Javadoc. JBoss provides free documentation and an example with an Ant build that uses XDoc

Re: JBoss 2.4.x taskdef

On Friday 15 November 2002 08:36, David Jencks wrote: > I can't figure out what this task does and how it differs from xdoclet. What does xdoclet do? And will it allow me to generate my ejb-jars, jboss.xml automatically, without a known set of EJB's? My JBoss taskdef doesn't require a known se

Re: JBoss 2.4.x taskdef

I can't figure out what this task does and how it differs from xdoclet. david jencks On 2002.11.15 10:43:16 -0500 Tim Sheridan wrote: > I'm still working with JBoss 2.4.x and would find this ANT task > definition a > valuable addition to my build scripts. I would be happy to report on > testing >

Re: Can properties be returned to a calling ant script?

On Fri, 15 Nov 2002, Dave Rathnow <[EMAIL PROTECTED]> wrote: > P.S. What's the Ant command to write properties to a file? :) or , whatever you need 8-) Both are optional tasks. Stefan -- To unsubscribe, e-mail: For additional commands, e-ma

RE: JBoss 2.4.x taskdef

Great! Looking forward to giving it a spin. -Original Message- From: Daniel Bruce Lynes [mailto:dlynes@;shaw.ca] Sent: Friday, November 15, 2002 11:29 AM To: Ant Users List Subject: Re: JBoss 2.4.x taskdef On Friday 15 November 2002 07:43, Tim Sheridan wrote: > I'm still working with JB

Re: JBoss 2.4.x taskdef

On Friday 15 November 2002 07:43, Tim Sheridan wrote: > I'm still working with JBoss 2.4.x and would find this ANT task definition > a valuable addition to my build scripts. I would be happy to report on > testing it for with my build scripts if that would help make it part of the > next ANT relea

RE: Can properties be returned to a calling ant script?

I suppose relative paths will suffice, though I was hoping to avoid having to have to code all relative path vars in all build scripts. I'm sure there is an easy way, or perhaps I'm making this more complicated than need be. I'll try what everyone has suggested. Thanks everyone, for your help!

caught exception

Ant 1.5.1, J2SDK1.4.1_01, Win2000, PIII 600Mhz, 256MB. I have 2 probs; 1) Ant runs ok for a test buildfile containing only an task. However it takes up to 100 seconds to run and states "The system cannot find the path specified". ANT_HOME, JAVA_HOME, CLASSPATH and PATH all seem set ok. 2) If

Re: PropertyFile Task Entry Value Attribute

Thanks for your response... I have it working now. -Ben At 03:46 AM 11/15/02 -0500, Erik Hatcher wrote: What you show should work, if I'm not missing the question entirely. Whats the problem you're experiencing? -- To unsubscribe, e-mail:

Re: Can properties be returned to a calling ant script?

On Fri, 15 Nov 2002, Dave Rathnow <[EMAIL PROTECTED]> wrote: > However, I don't see how this will solve the problem > of location independence. Do you need something more than relative paths to the property file(s) like David suggests? Stefan -- To unsubscribe, e-mail:

RE: PVCS

We are able to call PVCS from ANT, but only after extending and modifying the task that ships with ANT. We found that the current task only works on previous versions of Version Manager, and then only if you have not configured any security/permissions in your repository (!!) Basically the modi

RE: Can properties be returned to a calling ant script?

../../.. gives you location independence. If all your projects are part of the same CVS sandbox, then you know exactly the relative path to the properties file, so no sweat!!! Otherwise, you could define a single environment variable for the root, and refer to it instead of hard-coding paths. --DD

RE: Can properties be returned to a calling ant script?

your properties file should always be accessible using relative paths from your build script. d. -Original Message- From: Dave Rathnow [mailto:dave.rathnow@;wrx-ca.com] Sent: Friday, November 15, 2002 10:55 AM To: 'Ant Users List' Subject: RE: Can properties be returned to a calling

RE: Can properties be returned to a calling ant script?

The property file approach seems to be the most common. However, I don't see how this will solve the problem of location independence. I need some way of finding the root of our development tree. If I use a property file, that means I have to hard code the root location in a property, which doe

RE: JBoss 2.4.x taskdef

I'm still working with JBoss 2.4.x and would find this ANT task definition a valuable addition to my build scripts. I would be happy to report on testing it for with my build scripts if that would help make it part of the next ANT release as an optional task. Regards, Tim Sheridan -Original M

RE: Can properties be returned to a calling ant script?

Why don't you put all your common properties in a properties file which is included in all build scripts via: Jake At 08:21 AM 11/15/2002 -0700, you wrote: > > 2. Can you have a called Ant script define properties which > > can be picked up by the calling Ant script. > > Write them to a file

Re: Can properties be returned to a calling ant script?

On Fri, 15 Nov 2002, Dave Rathnow <[EMAIL PROTECTED]> wrote: > I would like to have a way that all common properties are set in a > single build script so I don't have to modify all my build scripts > if changes are made. > > Can you suggest another method? Set them in the build script that is ca

RE: Can properties be returned to a calling ant script?

Why not just put all of those properties in a .properties file and import them in each build script? You can even further extend this approach by allowing the users to provide over-rides to these as follows: regards, d. -Original Message- From: Dave Rathnow [mailto:dave.rathnow@;w

RE: Can properties be returned to a calling ant script?

> > 2. Can you have a called Ant script define properties which > > can be picked up by the calling Ant script. > > Write them to a file that gets read back in by the parent build > process. Most of the time, you don't want to do this 8-) Okay, I'll bite. Why isn't this a good idea? I would l

jspc and webinc

I'm using Ant 1.5.1 with Tomcat 4.1.12. I'm using the JspC task and have a question about the webinc attribute. First, it isn't in the task description in docs/manual/OptionalTasks/jspc.html but there is reference to it in docs/manual/api/org/apache/tools/ant/taskdefs/optional/jsp/JspC.html I tr

task

Just posted the latest version of the task. Provided AS-IS, use at your own risk. A caveat I fell into myself is using two with the same destination directory, which basically annihilate each other... --DD http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12632 -Original Message- From:

Re: fileset: exlude a dir not to be touched by ant?

On Fri, 15 Nov 2002, Rolf Schumacher <[EMAIL PROTECTED]> wrote: > do not know what you mean by "File#list". exactly what you've done 8-) > What I thought is that Ant shoulde to stop here, not going further. This is what I'd expect as well (haven't looked at the actual code for months, though).

Re: fileset: exlude a dir not to be touched by ant?

Thanks, Stefan. Sorry I'm not so professional in Ant - do not know what you mean by "File#list". What I've done is a simle Test: import java.io.File; public class Test { public static void main(String[] args) { File[] fs = (new File("C:\\")).listFiles(); for(int i=0; i

Re: PropertyFile Task Entry Value Attribute

What you show should work, if I'm not missing the question entirely. Whats the problem you're experiencing? Erik Benjamin Lubin wrote: How do I get property expansion to occur in the value attribute of an element in of the optional task? For example: Thanks -- To unsubscribe, e-