|
|
|
|
|
Re: Inheritance - eclipse plugins vs. java [message #756213 is a reply to message #756209] |
Fri, 11 November 2011 09:04  |
Eclipse User |
|
|
|
Hi,
If I get the problem right the problem is something that is a mismatch
between PDE&javac und JVM.
Bundle A:
---------
class A {
public void m() {
}
}
Bundle B requires A:
--------------------
class B extends A {
public void m2() {
}
}
Bundle C requires B:
--------------------
class C {
void main() {
new B().m(); // javac will cry
}
}
The problem here really is the compile time as Jeff described in his
blog because at runtime this would work perfectly.
Tom
Am 11.11.11 14:47, schrieb Paul Webster:
> You've tightly coupled A and B, and re-exporting is the sledge hammer.
> In effect you're saying that consumers should use B and that A is a
> meaningless module ... which begs the question, why not just suck A into
> B and get rid of the extraneous plugin?
>
> C should simply import the A package or require the A bundle. It
> obviously has a dependency on A, especially at the superclass level
> since it needs A.M1.
>
> PW
>
|
|
|
Powered by
FUDForum. Page generated in 0.04065 seconds