Bug 49758 - dump only changed classes
Summary: dump only changed classes
Status: REOPENED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: 1.1.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-09 03:33 EST by Wes Isberg CLA
Modified: 2009-08-30 02:48 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wes Isberg CLA 2004-01-09 03:33:21 EST 
As suggested by William Louth on aspectj-users, could the compiler support a
flag to only dump unchanged classes?  That would permit a simple copy rule for
updating jars and provide the SCM world with concrete de-minimus proof and
protection against aspects gone wild.  It might soothe some of the pain if we
don't fully support -outjar.

For those interested in contributing a patch on point, Jim suggested how to
implement this: modify the method
org.aspectj.weaver.bcel.BcelWeaver.dumpUnchanged to do nothing.
Comment 1 Adrian Colyer CLA 2005-08-26 11:02:27 EDT 
We're not going to get to this in AJ 1.5.0. Marking as "LATER" for consideration
in 1.5.1 and future release planning.

A submitted patch would increase the chances of this getting back into plan...
Comment 2 Eclipse Webmaster CLA 2009-08-30 02:48:23 EDT 
LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.