Yes, this is because the inpath argument will take all files located at a particular source root, run them through the weaver, and spit the results out at a different location. It doesn't make sense to do this to only a subset of files at a location.
Rather than trying to fiddle with the inpath argument, a better approach would be to tailor your aspects so that they only touch the subset of files that you are interested in (eg- using the within(<type_pattern>) pointcut.
On Tue, Jun 30, 2009 at 5:06 AM, Tahir Akhtar
<tahir@...> wrote:
Hi,
I am integrating aspectj compile-time-weaving in an existing ant-based
build.
I tried limiting <inpath> with ant's fileset combined with a <modified>
selector. But its not working. It appears inpath only supports simple
<path>s.
Is there a way to achieve this?
Regards
Tahir Akhtar
_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users
