Hello Eric,
I am having a bit of trouble understanding how to put the code together for
javac to read in
I have not tried the below yet - Obviously it wont work - But i dont
understand how to parse the file into - or how to let javac know that it
should compile from the bean.txt
<target name="compile" depends="init">
<!-- Compile the java code from ${src} into ${build} -->
<javac srcdir="${cfnCoreDB}" destdir="${buildCfn}"
<patternset>
<includesfile name="d:\scripts\cfn\bean.txt" />
<patternset/>
</target>
Also - What should my bean.txt look like - At the moment i have each java
file listed on every line
Even this example - Looks closer to what i want but - when you tell javac
src path - Would it compile everything in src and src2 then
<javac destdir="${buildcfn}"
debug="on">
<src path="${src}"/>
<src path="${src2}"/>
<includesfile name="d:\scripts\cfn\bean.txt"/>
</javac>
Please Advise
Thanks
-----Original Message-----
From: Erik Hatcher [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 28, 2002 10:11 AM
To: Ant Users List
Subject: Re: ANT Capability
Look at the patternset includesfile capability. You can incorporate that
into <javac>.
Erik
----- Original Message -----
From: "Atluri, Vamsi NYC" <[EMAIL PROTECTED]>
To: "'Ant Users List'" <[EMAIL PROTECTED]>
Sent: Thursday, February 28, 2002 9:51 AM
Subject: RE: ANT Capability
> Agreed - And yes that is something that i would want to do once the
> application is fully developed.
>
> right now the application is broken up into units - eg. project\db
>
> \security
>
> \util
> etc...
>
> But the thing is that - The project is not fully developed and there are
> many dependencies between java files - We are in a rapid development mode
at
> the current time - And my developers would like to do builds at any given
> point - So if they add a new java file the can compile all the working
units
> at any point in time. I understand that there is the includes option
> available - But is there any way that i can create a text file - comma
> delimitted, or spaces or new lines for each piece of code - This file
could
> be maintained by each individual developer and read in by the ant script -
> That way there is not alot of work invovled when compiling
>
> Basically
>
> ant -buildfile build.xml filelist.txt
>
> "$1" would be the a file in the filelist getting parsed into the build.xml
>
> -- contents -- build.xml
>
> <target name="compile">
> <!-- Compile the java code from ${src} into ${build} -->
> <javac srcdir="$1" destdir="${buildCore}"/>
> </target>
>
> Thanks,
> VA
>
> -----Original Message-----
> From: Erik Hatcher [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 27, 2002 5:59 PM
> To: Ant Users List
> Subject: Re: ANT Capability
>
>
> Huh? Ant can compile the entire tree. Multiple trees, in fact, in one
shot.
>
> Is that not what you want?
>
> Erik
>
>
> ----- Original Message -----
> From: "Atluri, Vamsi NYC" <[EMAIL PROTECTED]>
> To: "Ant Users List (E-mail)" <[EMAIL PROTECTED]>
> Sent: Wednesday, February 27, 2002 5:44 PM
> Subject: ANT Capability
>
>
> > Currently the project i am working on is pretty immature at the moment
and
> > will be growing rapidly in the next few weeks
> >
> > As you know there are many dependencies between java files during
compile
> > time
> >
> > Is there a way that i can create a generic ANT build file that - let say
> > reads a txt file containing the name and location of a java file that
need
> > to be compiled.
> >
> > This would allow my developers to update the txt file - By adding the
new
> > component in its heirarchial place within the txt file, that way the ant
> > script does not have to change ?
> >
> > Thanks,
> > VA
> >
> > --
> > To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
