ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <>
Subject RE: Unbundling copying support files from the javac task
Date Mon, 06 Mar 2000 22:23:25 GMT

The problem is that there tends to be other files that end up being copied
across that you don't really want. For example, CVS can leave versions of
files around when you do an update and there is a conflict., editors can
leave backup files, etc. My view is that you should be explicit about what
you want copied into the build area.

Of course, we could go for a backwards compatible attribute to control the

<javac copysupport="false" ...>

Each such option, however, adds to ant's complexity. It may be better to
reduce optionality rather than increase it.


> -----Original Message-----
> From: Twiggs, Glenn []
> Sent: Tuesday, 7 March 2000 9:06
> To: ''
> Subject: RE: Unbundling copying support files from the javac task
> The "copying support files" feature is one of the selling-points
> of ANT (at
> least for me), that I don't need to know all the details about setting up
> the "classes" directory. I like that "javac" is totally self-contained. Is
> there a situation where you would want to compile classes but not
> copy over
> the .properties file(s) used by those classes?
> Glenn.
> From: Kuiper, Arnout []
> > From: []
> > What I would like to propose is that the function to copy
> > support files be
> > removed from javac.  People who desire the current level of
> > functionallity
> > could simply add a
> >    <copydir excludes="**/*.java">
> > task to their build.xml files
> +1 for me!
>   Arnout

View raw message