Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » How to view sources of internal plugins
How to view sources of internal plugins [message #998547] Thu, 10 January 2013 08:08 Go to next message
Tuomas Heittola is currently offline Tuomas Heittola
Messages: 2
Registered: January 2013
Junior Member
I am using a target platform from another party.

My problem is that they have recently started using x-internal true in their exported packages. What this means to me is that I can't view the source codes anymore. I have the source jars and it is of course possible to unzip the source jars and view the source manually that way. It would be easier if I could just open the classes in Eclipse.

I know the dangers of using relying on packages that are marked as internal. But it would be quite important to see what is happening in the classes.

Is it possible to somehow view these classes in Eclipse?
Re: How to view sources of internal plugins [message #998750 is a reply to message #998547] Thu, 10 January 2013 16:09 Go to previous messageGo to next message
Dani Megert is currently offline Dani Megert
Messages: 3801
Registered: July 2009
Senior Member
On 10.01.2013 13:06, Tuomas Heittola wrote:
> I am using a target platform from another party.
>
> My problem is that they have recently started using x-internal true in
> their exported packages. What this means to me is that I can't view
> the source codes anymore. I have the source jars and it is of course
> possible to unzip the source jars and view the source manually that
> way. It would be easier if I could just open the classes in Eclipse.
>
> I know the dangers of using relying on packages that are marked as
> internal. But it would be quite important to see what is happening in
> the classes.
>
> Is it possible to somehow view these classes in Eclipse?
Marking the stuff x-internal is probably not the issue but rather that
they no longer provide the source plug-ins (correctly). If you have the
source then you can e.g. import the bundles from the target and then
manually attach the source. After that you will be able to see the
source when opening a type.

Dani
Re: How to view sources of internal plugins [message #1000807 is a reply to message #998750] Tue, 15 January 2013 13:04 Go to previous messageGo to next message
Tuomas Heittola is currently offline Tuomas Heittola
Messages: 2
Registered: January 2013
Junior Member
Thanks, that helps a bit.

I wish there was a way to allow opening the types without importing though. There are nearly 600 plugins, so importing them all is not really that convenient and importing them one by one when I need them seems a bit inconvenient too.
What confuses me is that the packages without x-internal open without importing them.
Re: How to view sources of internal plugins [message #1002338 is a reply to message #1000807] Fri, 18 January 2013 12:25 Go to previous message
sumit singh is currently offline sumit singh
Messages: 131
Registered: October 2012
Location: Bangalore
Senior Member

From bundle_manifest

The x-internal Directive
The x-internal directive can be used in an Export-Package header to specify whether the package is an internal package. The Plug-in Development Environment will discourage other bundles from using an internal package. If the x-internal directive is not specified then a default value of 'false' is used. The x-internal directive must use the following syntax:

x-internal ::= ( 'true' | 'false' )

The following is an example of the x-internal directive:

Export-Package: org.eclipse.foo.internal; x-internal:=true

Previous Topic:Add the Console to an Eclipse 4 RCP Application
Next Topic:table cell editor does not deactivate and commit the value when save command is invoked
Goto Forum:
  


Current Time: Thu Oct 30 23:44:54 GMT 2014

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

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