Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » General (non-technical) » Eclipse Foundation » Re: Has Eclipse Open Source Policy Changed?
Re: Has Eclipse Open Source Policy Changed? [message #497192] Thu, 12 November 2009 19:24 Go to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 26237
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 #497347 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497350 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497362 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497368 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497371 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497375 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497378 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497386 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497400 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497403 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497407 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497419 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497424 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497430 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497438 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497441 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497449 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497452 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497463 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497467 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497472 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497480 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497499 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497505 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497509 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497520 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497531 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497550 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497569 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497572 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497584 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497607 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497610 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497615 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497637 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497644 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497653 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497659 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to next message
Bill Winspur is currently offline Bill WinspurFriend
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 #497668 is a reply to message #497192] Thu, 12 November 2009 22:26 Go to previous messageGo to previous message
Bill Winspur is currently offline Bill WinspurFriend
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.
Previous Topic:Has Eclipse Open Source Policy Changed?
Next Topic:Why are Bugzilla bugs not crawled by search engines?
Goto Forum:
  


Current Time: Fri Nov 28 21:06:52 GMT 2014

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

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