Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » issues with source plug-ins / features
issues with source plug-ins / features [message #505345] Tue, 29 December 2009 18:54 Go to next message
Volker Wegert is currently offline Volker WegertFriend
Messages: 169
Registered: July 2009
Senior Member
Hi all,

I don't understand a certain behaviour of the "Import Plug-In as Source
Project" function (right-click a plug-in in the Plug-Ins view, then choose
Import As --> Source Project. If I do this with, say, org.eclipse.core.jobs, I
get a source project the way I expect it to be. If I try the same thing with
one of my plug-ins, I get a new plug-in project, but without the sources -
there's a jar that contains the compiled classes and that's about it. Also, I
can't open the source of the classes contained in my plug-ins. The source
plug-in (generated by PDE build) does contain the sources - I can see that
when executing "Import Plug-In as Source Project", it generates a project with
a src folder and all included plug-ins below. I'd say there's some missing
link between the source plug-in and the rest of the world, but where might
that be? I don't really understand what might be missing - do you have any
suggestions where to look?

Thanks
Volker


--
* Volker Wegert * http://www.volker-wegert.de/contact *
31.69 nHz = once a year.
Re: issues with source plug-ins / features [message #505606 is a reply to message #505345] Sat, 02 January 2010 20:46 Go to previous messageGo to next message
Jens Mayer is currently offline Jens MayerFriend
Messages: 19
Registered: September 2009
Location: Hamburg
Junior Member
Hi Volker,

I encountered exactly the same problem with 3rd-party-bundles from
springsource bundle repository. Let me know if you find out anything...

Jens

Volker Wegert schrieb:
> Hi all,
>
> I don't understand a certain behaviour of the "Import Plug-In as Source
> Project" function (right-click a plug-in in the Plug-Ins view, then choose
> Import As --> Source Project. If I do this with, say, org.eclipse.core.jobs, I
> get a source project the way I expect it to be. If I try the same thing with
> one of my plug-ins, I get a new plug-in project, but without the sources -
> there's a jar that contains the compiled classes and that's about it. Also, I
> can't open the source of the classes contained in my plug-ins. The source
> plug-in (generated by PDE build) does contain the sources - I can see that
> when executing "Import Plug-In as Source Project", it generates a project with
> a src folder and all included plug-ins below. I'd say there's some missing
> link between the source plug-in and the rest of the world, but where might
> that be? I don't really understand what might be missing - do you have any
> suggestions where to look?
>
> Thanks
> Volker
>
>
Re: issues with source plug-ins / features [message #505778 is a reply to message #505606] Mon, 04 January 2010 17:02 Go to previous messageGo to next message
Volker Wegert is currently offline Volker WegertFriend
Messages: 169
Registered: July 2009
Senior Member
Hi.

Jens Mayer <jens.mayer1@gmx.de> writes:
>> I don't understand a certain behaviour of the "Import Plug-In as Source
>> Project" function (right-click a plug-in in the Plug-Ins view, then choose
>> Import As --> Source Project. If I do this with, say,
>> org.eclipse.core.jobs, I get a source project the way I expect it to be. If
>> I try the same thing with one of my plug-ins, I get a new plug-in project,
>> but without the sources - there's a jar that contains the compiled classes
>> and that's about it. Also, I can't open the source of the classes contained
>> in my plug-ins. The source plug-in (generated by PDE build) does contain
>> the sources - I can see that when executing "Import Plug-In as Source
>> Project", it generates a project with a src folder and all included
>> plug-ins below. I'd say there's some missing link between the source
>> plug-in and the rest of the world, but where might that be? I don't really
>> understand what might be missing - do you have any suggestions where to
>> look?
> I encountered exactly the same problem with 3rd-party-bundles from
> springsource bundle repository. Let me know if you find out anything...

I was able to reproduce the issue with a minimal example, and I think it's a
bug --> 298799. Feel free to smash the documentation I've failed to notice to
the back of my head. :-)

Thanks
Volker

--
* Volker Wegert * http://www.volker-wegert.de/contact *
141 Reasons why you can't find your system administrator: 60. They're at a
travel agent's, booking a vacation to friendlier place, like Iraq.
Re: issues with source plug-ins / features [message #506287 is a reply to message #505606] Wed, 06 January 2010 06:56 Go to previous message
Volker Wegert is currently offline Volker WegertFriend
Messages: 169
Registered: July 2009
Senior Member
Jens Mayer <jens.mayer1@gmx.de> writes:
> Volker Wegert schrieb:
>> I don't understand a certain behaviour of the "Import Plug-In as Source
>> Project" function (right-click a plug-in in the Plug-Ins view, then choose
>> Import As --> Source Project. If I do this with, say, org.eclipse.core.jobs, I
>> get a source project the way I expect it to be. If I try the same thing with
>> one of my plug-ins, I get a new plug-in project, but without the sources -
>> there's a jar that contains the compiled classes and that's about it. Also, I
>> can't open the source of the classes contained in my plug-ins. The source
>> plug-in (generated by PDE build) does contain the sources - I can see that
>> when executing "Import Plug-In as Source Project", it generates a project with
>> a src folder and all included plug-ins below. I'd say there's some missing
>> link between the source plug-in and the rest of the world, but where might
>> that be? I don't really understand what might be missing - do you have any
>> suggestions where to look?
> I encountered exactly the same problem with 3rd-party-bundles from
> springsource bundle repository. Let me know if you find out anything...

It's very simple, once you know the details - the feature has to include the
source plug-in with unpack="true" set for old-style source plug-ins. Details
are in the bug.

HTH
Volker

--
* Volker Wegert * http://www.volker-wegert.de/contact *
The computer revolution is over. The computers won.
Re: issues with source plug-ins / features [message #603913 is a reply to message #505345] Sun, 03 January 2010 01:43 Go to previous message
Jens Mayer is currently offline Jens MayerFriend
Messages: 19
Registered: September 2009
Location: Hamburg
Junior Member
Hi Volker,

I encountered exactly the same problem with 3rd-party-bundles from
springsource bundle repository. Let me know if you find out anything...

Jens

Volker Wegert schrieb:
> Hi all,
>
> I don't understand a certain behaviour of the "Import Plug-In as Source
> Project" function (right-click a plug-in in the Plug-Ins view, then choose
> Import As --> Source Project. If I do this with, say, org.eclipse.core.jobs, I
> get a source project the way I expect it to be. If I try the same thing with
> one of my plug-ins, I get a new plug-in project, but without the sources -
> there's a jar that contains the compiled classes and that's about it. Also, I
> can't open the source of the classes contained in my plug-ins. The source
> plug-in (generated by PDE build) does contain the sources - I can see that
> when executing "Import Plug-In as Source Project", it generates a project with
> a src folder and all included plug-ins below. I'd say there's some missing
> link between the source plug-in and the rest of the world, but where might
> that be? I don't really understand what might be missing - do you have any
> suggestions where to look?
>
> Thanks
> Volker
>
>
Re: issues with source plug-ins / features [message #603930 is a reply to message #603913] Mon, 04 January 2010 21:47 Go to previous message
Volker Wegert is currently offline Volker WegertFriend
Messages: 169
Registered: July 2009
Senior Member
Hi.

Jens Mayer <jens.mayer1@gmx.de> writes:
>> I don't understand a certain behaviour of the "Import Plug-In as Source
>> Project" function (right-click a plug-in in the Plug-Ins view, then choose
>> Import As --> Source Project. If I do this with, say,
>> org.eclipse.core.jobs, I get a source project the way I expect it to be. If
>> I try the same thing with one of my plug-ins, I get a new plug-in project,
>> but without the sources - there's a jar that contains the compiled classes
>> and that's about it. Also, I can't open the source of the classes contained
>> in my plug-ins. The source plug-in (generated by PDE build) does contain
>> the sources - I can see that when executing "Import Plug-In as Source
>> Project", it generates a project with a src folder and all included
>> plug-ins below. I'd say there's some missing link between the source
>> plug-in and the rest of the world, but where might that be? I don't really
>> understand what might be missing - do you have any suggestions where to
>> look?
> I encountered exactly the same problem with 3rd-party-bundles from
> springsource bundle repository. Let me know if you find out anything...

I was able to reproduce the issue with a minimal example, and I think it's a
bug --> 298799. Feel free to smash the documentation I've failed to notice to
the back of my head. :-)

Thanks
Volker

--
* Volker Wegert * http://www.volker-wegert.de/contact *
141 Reasons why you can't find your system administrator: 60. They're at a
travel agent's, booking a vacation to friendlier place, like Iraq.
Re: issues with source plug-ins / features [message #604000 is a reply to message #603913] Wed, 06 January 2010 06:56 Go to previous message
Volker Wegert is currently offline Volker WegertFriend
Messages: 169
Registered: July 2009
Senior Member
Jens Mayer <jens.mayer1@gmx.de> writes:
> Volker Wegert schrieb:
>> I don't understand a certain behaviour of the "Import Plug-In as Source
>> Project" function (right-click a plug-in in the Plug-Ins view, then choose
>> Import As --> Source Project. If I do this with, say, org.eclipse.core.jobs, I
>> get a source project the way I expect it to be. If I try the same thing with
>> one of my plug-ins, I get a new plug-in project, but without the sources -
>> there's a jar that contains the compiled classes and that's about it. Also, I
>> can't open the source of the classes contained in my plug-ins. The source
>> plug-in (generated by PDE build) does contain the sources - I can see that
>> when executing "Import Plug-In as Source Project", it generates a project with
>> a src folder and all included plug-ins below. I'd say there's some missing
>> link between the source plug-in and the rest of the world, but where might
>> that be? I don't really understand what might be missing - do you have any
>> suggestions where to look?
> I encountered exactly the same problem with 3rd-party-bundles from
> springsource bundle repository. Let me know if you find out anything...

It's very simple, once you know the details - the feature has to include the
source plug-in with unpack="true" set for old-style source plug-ins. Details
are in the bug.

HTH
Volker

--
* Volker Wegert * http://www.volker-wegert.de/contact *
The computer revolution is over. The computers won.
Previous Topic:target definition requires javax.crypto.spec
Next Topic:How to set up cross/hybrid target platform for RCP and RAP plugins?
Goto Forum:
  


Current Time: Fri Dec 19 01:47:56 GMT 2014

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

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