Hi Joel, I'm afraid you cannot do that. If your aspects are using !within() pointcuts to correctly exclude code they do not want to weave, the weaving process for code that does not match should be very quick. Given that the AspectJ compiler is the eclipse compiler at its heart, if there is no weaving of a file then performance should be comparable between AspectJ and Eclipse compilation.
I would rather look to fix performance of project building as a whole than allow source code to be split up. Are you finding it is full compilation that is slow? Or incremental compilation? I don't have any open issues for the speed of compilation, so perhaps you should open one and describe the scenario if you can. Collect timing output from the AJDT Event Trace view and include it too, that may be helpful. cheers, Andy. 2008/7/17 <[EMAIL PROTECTED]>: > I'm using eclipse 3.3 and the latest AJDT dev build. I have 11 source > directories in this project. I only need one or two of them to be > weaved by aspectJ. Is there a way to configure an eclipse project so > that it will compile some of the source directories with the eclipse > compiler and only the needed ones with the weaver? Using aspectj > builder on everything is rather slow. If could split it up like this > it would speed up building a great deal, I think. > > Thanks. > _______________________________________________ > aspectj-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/aspectj-users > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
