|Re: [equinox-dev] support for component API refactoring|
Clearly I have not thought deeply about this but superficially, the OSGi bundle markup gives you enough information to figure out where exactly each referenced class will come from. With this info, you should be able to correctly apply the transformations without accidents. You would have to do an analysis to see that the set of "new" classes does not overlap the set of existing classes but that should be pretty straightforward.
As for BCEL and ASM, yes, you would want some abstraction above this. I wonder if there are any really simple tools out there since the sort of transformations (at least initially) envisioned here are very simple (e.g., add some constant pool entries and change some constant pool references).