You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ant.apache.org by Wes Moulder <wm...@axyssolutions.com> on 2000/09/14 22:05:39 UTC

Javac taskdef

I've been having some problems with javac taskdef.  My source directories
contain extra files that I don't want copied over when I compile, but when I
run it, it compiles the source, and then copies the extra files, even though
it tells me that's deprecated, and that if I want it to do that I have to
copydir the directories.  I'm currently using ant 1.1.  Is this a problem
anyone else has had, and if so how do I stop it?  Am I missing an arguement
to the javac taskdef that will eliminate this behaviour?

Thanks in advance,
Wes

RE: Javac taskdef

Posted by Conor MacNeill <co...@ebinteractive.com.au>.

Wes,

Deprecated in this instance means that the Javac task does this but you
shouldn't rely on it to do it in the future. If you do need that behaviour
in the future you will need to use copydir. That is what the warning is
saying. All features of ant that were deprecated in release 1.1 have now
been removed. You can use a recent nightly build. If you want to continue to
use release 1.1 the best thing to do is to add an include element to your
javac like this

<javac ...>
   <include name="**/*.java"/>
</javac>

The warning and the copying should then go away.

Conor


--
Conor MacNeill
conor@cortexebusiness.com.au
Cortex eBusiness
http://www.cortexebusiness.com.au

> -----Original Message-----
> From: Wes Moulder [mailto:wmoulder@axyssolutions.com]
> Sent: Friday, 15 September 2000 7:06
> To: ant-user@jakarta.apache.org
> Subject: Javac taskdef
>
>
> I've been having some problems with javac taskdef.  My source directories
> contain extra files that I don't want copied over when I compile,
> but when I
> run it, it compiles the source, and then copies the extra files,
> even though
> it tells me that's deprecated, and that if I want it to do that I have to
> copydir the directories.  I'm currently using ant 1.1.  Is this a problem
> anyone else has had, and if so how do I stop it?  Am I missing an
> arguement
> to the javac taskdef that will eliminate this behaviour?
>
> Thanks in advance,
> Wes
>
>