| Has Eclipse Open Source Policy Changed? [message #497673] |
Thu, 12 November 2009 14:14  |
Eclipse User |
|
|
|
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.
|
|
|
|
| Re: Has Eclipse Open Source Policy Changed? [message #497675 is a reply to message #497674] |
Thu, 12 November 2009 17:26  |
| Eclipse User |
|
|
|
Ed Merks wrote:
> Bill,
>
> This has nothing to do with open source policies of the foundation. Not
> only that, I can still see Project when I use Ctrl-Shift-T to locate
> it. Perhaps you don't have the SDK installed in your environment?
>
Ed,
I do have the SDK. Ctrl-Shift-T takes me to the type select dialog,
which when the Project type is selected, pulls up a .class pane not a
..java pane. This is also what the Open Declaration (F3) does. It was
this behavior of hiding source that I have on the plug-in class-path,
which prompted me to check for open source policy changes. By policy
change I meant something like:
"Starting with galileo, source for internal packages ...."
Thanks for your response. If necessary, I'll pursue this on the platform
forum.
Bill.
|
|
|
Powered by
FUDForum. Page generated in 0.02960 seconds
Home