Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » General (non-technical) » Eclipse Foundation » Has Eclipse Open Source Policy Changed?
Has Eclipse Open Source Policy Changed? [message #497686] Thu, 12 November 2009 19:14 Go to next message
Bill Winspur is currently offline 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.
Re: Has Eclipse Open Source Policy Changed? [message #497687 is a reply to message #497686] Thu, 12 November 2009 19:24 Go to previous messageGo to next message
Ed Merks is currently offline Ed Merks
Messages: 26152
Registered: July 2009
Senior Member
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?


Bill Winspur wrote:
> 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 #497688 is a reply to message #497687] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill Winspur
Messages: 180
Registered: July 2009
Senior Member
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.
Re: Has Eclipse Open Source Policy Changed? [message #497689 is a reply to message #497688] Fri, 13 November 2009 05:17 Go to previous messageGo to next message
Prakash G.R. is currently offline Prakash G.R.
Messages: 621
Registered: July 2009
Senior Member
Bill Winspur wrote:
> 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

You need to check what is your target platform. Probably that doesn't
have the source. Either case, the code is always available from the CVS
with anonymous access. Its not hidden.

- Prakash

Platform UI Team, IBM
http://blog.eclipse-tips.com
Re: Has Eclipse Open Source Policy Changed? [message #500808 is a reply to message #497686] Sun, 29 November 2009 04:25 Go to previous message
linzuxiong  is currently offline linzuxiong
Messages: 15
Registered: November 2009
Junior Member
are you a asso?
Previous Topic:Eclipse DemoCamps, Nov. 29-Dec. 5: Austria, Germany, Hungary, U.S.
Next Topic:Eclipse DemoCamps, Dec. 6-12: Copenhagen, Florence, Nieuwegein
Goto Forum:
  


Current Time: Fri Oct 31 15:17:08 GMT 2014

Powered by FUDForum. Page generated in 0.16038 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software