On Thu, Aug 20, 2009 at 9:08 AM, Stefan Walter wrote:
> is there a good/elegant recipe for selecting those source files that javac
> chose to compile?
Yes. Introspect the .class files to know which source files they came from.
Assumes debug info in left in the .class, but you can tell javac that
Joe Schmetzer, 21.08.09, 10:14h CEST:
> You can use the selector:
> http://ant.apache.org/manual/CoreTypes/selectors.html#dependselect
>
> Use a glob mapper in the depend selector to match the java files to
> the corresponding class files, and the depend selector will pick out
> only those files
2009/8/21 Stefan Walter :
> David Weintraub, 20.08.09, 23:13h CEST:
>
>> Patternsets to the rescue!
>>
>>
>>
>>
>>
>>
>> > sourcepath="">
>>
>>
>>
>> Your different tasks can define different patternsets for source files.
>
> Thanks for your reply. That would certainly work; howeve
David Weintraub, 20.08.09, 23:13h CEST:
> Patternsets to the rescue!
>
>
>
>
>
>
> sourcepath="">
>
>
>
> Your different tasks can define different patternsets for source files.
Thanks for your reply. That would certainly work; however, I would have to
know the pattern in ad
Patternsets to the rescue!
Your different tasks can define different patternsets for source files.
On Thu, Aug 20, 2009 at 10:08 AM, Stefan Walter wrote:
> Hi,
>
> is there a good/elegant recipe for selecting those source files that javac
> chose to compile?
>
> I have a single
Hi,
is there a good/elegant recipe for selecting those source files that javac
chose to compile?
I have a single source directory containing the project's classes and
multiple targets compiling subsets of these classes into distinct
destination directories. For at least one of these subsets, I wo
