> -Original Message-
> From: Stefan Bodewig [mailto:[EMAIL PROTECTED]]
> > Is there anyway to access the arguments?
>
> ${ant.project.name} and ${basedir}, there is no property for the
> default target though. ${basedir} will be an absolute path BTW.
>
> The manual has a section labe
Given a project:
Is there anyway to access the arguments?
In an ideal world this would be via properties eg:
${project.name} = "tags"
${project.basedir} = "../.."
etc... Thanks,
Ian
___
CAZENOVE & CO.
DISCLAIMER, PLEASE NOTE:
This commu
> -Original Message-
> From: Ozzy Espaillat [mailto:[EMAIL PROTECTED]]
> Sent: 09 April 2001 16:13
> To: [EMAIL PROTECTED]
> Subject: RE: package puzzle
>
>
> Ant does a simple mapping from source to destination dir. It sees
> Prj/Prj.java and expects to see Prj/classes/Prj.class which
> -Original Message-
> From: Diane Holt [mailto:[EMAIL PROTECTED]]
> Sent: 09 April 2001 15:16
> To: [EMAIL PROTECTED]
> Subject: Re: package puzzle
>
>
> You'll most likely need to respecify the "srcdir" and, if
> you're including
> specific files, the path to where those files are f
Am confused... I have a project which I've been building with
Ant for some time. The classes have been at the default
package level.
Have just changed my classes to be in a named package.
The still project builds correctly, but it *always* compiles,
even when it is up to date!
Can return my p
> -Original Message-
> From: Conor MacNeill [mailto:[EMAIL PROTECTED]]
> If you want to create a dependency between A.class and
> b.class which is not
> reflected in the source, the you are right, and will
> not help you.
> I guess you can use uptodate as Diane suggested.
I've manage
5
> To: [EMAIL PROTECTED]
> Subject: Re: Make Dependencies
>
>
> Check out the task
> http://jakarta.apache.org/ant/manual/OptionalTasks/depend.html
>
> - Original Message -
> From: "Macey, Ian" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECT
How can I tell Ant that there is a dependency between two
.java files? ie Given a.java and b.java, how do I say in Ant,
if a.java is compiled then you must also compile b.java.
Have had various attempts, the problems are getting javac
to compile b.java even though b.class is later than b.java,
