| Classpath bug when resolving property editors? [message #123351] |
Wed, 19 April 2006 05:42 |
Eclipse User |
|
|
|
I have a project A that depends on B.
B then depends on C.
B also exports the dependency on C.
In this configuration my property editors from bean info's that are defined
in A are not picked up.
Code doesn't get generated as the PropertyEditor isn't found so the
getJavaInitializationString
clearly can't be called. Additionally, the line for my property in the
properties editor that has a custom editor doesn't have a button for opening
the custom property editor.
The customizers are however picked up.
If I change the dependencies of the projects to make A depend explicitly on
B AND C,
then both customizers and property editors are picked up, and code
generation works properly,
and there is a button that opens up the custom editor.
This seems like a bug to me.
What do you think?
|
|
|
Powered by
FUDForum. Page generated in 0.03446 seconds
Home