Has Eclipse Open Source Policy Changed? [message #497195] |
Thu, 12 November 2009 19:14 |
Bill Winspur Messages: 180 Registered: July 2009 |
Senior Member |
|
|
It seems that access to the source code of Eclipse is not quite as open
as it used to be, which I assume is a policy issue to explore in this forum.
1. On Ganymede, I can see the source code of internal classes such
as:
org.eclipse.core.internal.resources.Project
simply by performing a Show Declaration... operation on selected
reference to it in the java editor. The source code then opens in
another editor pane.
2. However, on Galileo the same operation results in opening a
.class read-only pane showing psuedo-code compiled from a class
file. At the top of the listing is the following unselectable text:
"The JAR of this class file belongs to container
'Plug-in Dependencies' which does not allow
modifications to source attachments on its entries."
Has the policy of accessibility to internal code (openness) in Eclipse
changed ?
Can one conveniently browse 'internal' source in Galileo, as was
possible in Ganymede ?
Bill.
|
|
|
Powered by
FUDForum. Page generated in 0.22898 seconds