Bug 492204 - Manually attached sources are reset after a workspace restart
Summary: Manually attached sources are reset after a workspace restart
Status: REOPENED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-21 15:12 EDT by Fred Bricon CLA
Modified: 2023-12-11 07:34 EST (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fred Bricon CLA 2016-04-21 15:12:35 EDT
When you manually attach sources to jars from the "Plug-in Dependencies" classpath container, they are reset after the workbench is restarted.

Fortunately, https://marketplace.eclipse.org/content/pde-source-lookup makes it bearable by automatically reattaching the missing sources.

My guess is the "Plug-in Dependencies" container's state need to be serialized on disk, after classpath entries have been updated, so it can be restored on restart. This is how m2e's Maven classpath container works.
Comment 1 Mickael Istria CLA 2016-11-10 08:39:31 EST
It's frustrating to require an external plugin to fix that. Is there any chance to have it fixed by 4.7 ?
Comment 2 Eclipse Genie CLA 2019-01-02 13:28:13 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Lars Vogel CLA 2019-09-02 14:59:10 EDT Comment hidden (obsolete)
Comment 4 Lars Vogel CLA 2019-09-02 15:07:02 EDT Comment hidden (obsolete)
Comment 5 Lars Vogel CLA 2021-12-16 09:05:00 EST
Re-opening as I hear from a client that this problem still exists.
Comment 6 Lars Vogel CLA 2021-12-16 09:07:50 EST
AFAIK the pde source lookup has been migrated to PDE. Philipp, can you still reproduce with the latest release?
Comment 7 Philipp Bauer CLA 2021-12-16 10:03:41 EST
The problem persists in 2021-12.
Comment 8 Fred Bricon CLA 2021-12-16 11:40:51 EST
(In reply to Lars Vogel from comment #6)
> AFAIK the pde source lookup has been migrated to PDE. 

You mean the same feature as my plugin has been implemented natively in PDE? I was not aware of that, do you have some link?
Comment 9 Philipp Bauer CLA 2021-12-20 09:06:00 EST
And as far as I could tell the pde-source-lookup plugin only supports reattaching, if the jars in the Plug-in Dependencies have attached sources, is that correct?
Comment 10 Philipp Bauer CLA 2021-12-20 09:06:00 EST
And as far as I could tell the pde-source-lookup plugin only supports reattaching, if the jars in the Plug-in Dependencies have attached sources, is that correct?
Comment 11 Philipp Bauer CLA 2021-12-20 09:06:24 EST
And as far as I could tell the pde-source-lookup plugin only supports reattaching, if the jars in the Plug-in Dependencies have attached sources, is that correct?
Comment 12 Fred Bricon CLA 2021-12-20 09:13:38 EST
pde-source-lookup reattaches sources if it finds matching source jars from known locations (local .m2 repo or ~/.eclipse/org.jboss.tools.pde.sourcelookup.core/sources)
Comment 13 Eclipse Genie CLA 2023-12-11 07:34:29 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.