Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: <491050BC.9070804@ptc.com>
Date: Tue, 04 Nov 2008 07:40:12 -0600
From: Jess Holle <jessh@ptc.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: Re: javac task problem in Java 6
References: <22ac04340810301122v241cd885oc61d6a4b45a008d9@mail.gmail.com>
	<geo84d$e46$1@ger.gmane.org>
	<22ac04340811040207lb2a47fes9ffcb1c4014350b9@mail.gmail.com>
 <y1uvdv3lo3i.fsf@v30161.1blu.de>
In-Reply-To: <y1uvdv3lo3i.fsf@v30161.1blu.de>
Content-Type: multipart/alternative;
 boundary="------------020606010706080003060802"

--------------020606010706080003060802
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I am rather certain this is a javac bug -- though it would be good to 
/prove /that from a javac command line so as to get some focus on the 
real issue here.

I believe Sun should take this particular issue seriously.  We've seen 
this before where A depends on B which /internally/ depends upon C and 
then suddenly one has to have C around to compile A.  That extends 
compilation dependencies across decoupling points one designs in and 
breaks library opacity / encapsulation.  This whole issue needs to be 
taken seriously and nailed by Sun.  It impacts Ant, of course, but this 
in turn impacts NetBeans.  It also impacts everything that uses their 
compiler rather than JDT.  Overall this issue should not be tolerated.

--
Jess Holle

Stefan Bodewig wrote:
> On Tue, 4 Nov 2008, Sergey Bondarenko <enterit@gmail.com> wrote:
>
>   
>> Regarding compilation issue, it looks like Ant javac task does not
>> handle "includes" and "excludes" attributes correctly when it is
>> used with JDK 6.  But it works properly with JDK 5.
>>     
>
> Uhm, no.
>
> includes/excludes controls which source files are being sent to
> javac's command line.  If javac decides that it needs to compile
> additional classes that it can find inside the source path, then there
> is nothing that Ant can do.
>
> Inside the manual page for the javac task you will find (under
> examples):
>
> ,----
> | If you wish to compile only files explicitly specified and disable
> | javac's default searching mechanism then you can unset the sourcepath
> | attribute:
> | 
> |   <javac sourcepath="" srcdir="${src}"
> |          destdir="${build}" >
> |     <include name="**/*.java"/>
> |     <exclude name="**/Example.java"/>
> |   </javac>
> | 
> | That way the javac will compile all java source files under "${src}"
> | directory but skip the examples. The compiler will even produce errors
> | if some of the non-example files refers to them.
> `----
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
>   


--------------020606010706080003060802--