|Large jar on InPath [message #587829]
||Sat, 23 April 2005 11:35
| Barry Kaplan
Registered: July 2009
I have a somewhat large jar on the InPath of my aspectj project (about 4M). I only need to weave a very few classes out of this jar, but do not own the jar and cannot have it built as smaller jars. Any incremental compile seems to require scanning the entire jar each time. The progress quickly goes to 11%, then spends about 30 seconds there before completing. This means 30 seconds for every single incremental compile. Not very productive.|
Is there any way to speed this up? Are InPath jars cached in any way? Can they be?
When I try to edit the 'Access rules' for the InPath jar no dialog is presented (ie, I click the button but nothing happens). It seems that filtering the classes considered for weaving via the access rules would be my problem solver. Is this is a known problem, or just not implemented? Need I file a bug?
(eclipse 3.1M6, java5 compiler, ajdt build 1.2.0 20050420095141)
(BTW, this is in a freshly created project. I still cannot get around the compile error I posted the other day for a different exiting project.)
Powered by FUDForum
. Page generated in 0.01790 seconds