[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [e4-dev] Re-exporting Require-Bundle
|
In Ben's case it is most likely he's a replacer, not the re-exporter.
IIRC RAP needs to replace a number of classes in the workbench, and it
is hard to do because of our re-exporting and our reliance on
Require-Bundle
PW
While you're right that has nothing to do with this discussion.
Reexporting bundles is not the problem for RAP but it's something I
stumbled several times. Regarding the Require-Bundle vs. Import-Package
- that's another point but should be discussed in another thread ;-)
One example regarding reexport: several eclipse projects have
Require-Bundle on com.ibm.icu. As some of us want to use
com.ibm.icu.base I talked to the teams to use Import-Package for this
case. The problem was:
They can't do it because they already reexported com.ibm.icu and cannot
break their clients. These are the day-to-day problems I see with
reexporting bundles because you have a much tighter coupling between
bundles.
Just my 2 cents
Ben
