Jesse Glick wrote:
Nicola Ken Barozzi wrote:
While I agree that there is some commonality across many Java
projects (in that Java has a packaging mechanism that utilizes
directories etc. and that these projects commonly produce one or
more JAR files) it seems to me that this approach would either
Nicola Ken Barozzi wrote:
While I agree that there is some commonality across many Java
projects (in that Java has a packaging mechanism that utilizes
directories etc. and that these projects commonly produce one or
more JAR files) it seems to me that this approach would either be
too restrictive
> > It seems to me that there are as many completely different ways of
> > using Ant as there are projects in this world. If you were to supply a
> > "standard" build script, ready for customization, what input file
> > structure would it expect? What language would be compiled (if any)?
> > What d
Phil Weighill-Smith wrote:
I'm not trying to rain on anyone's parade, but have you considered...
It seems to me that there are as many completely different ways of
using Ant as there are projects in this world. If you were to supply a
"standard" build script, ready for customization, what input fil
to obtain dependency JARs
from other projects
Phil :n.
-Original Message-
From: news on behalf of Nicola Ken Barozzi
Sent: Sat 18/12/2004 11:16
To: [EMAIL PROTECTED]
Cc:
Subject: [RT] Define common project properties and tasks
If Ant defines a name for common project properties, then each task
could have a parallel typedef that configures it with these values.
In this way, a basic user would only need to write a property file and
call the extended tasks without attributes, and have them work correctly
OOTB.
Same thi
