Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336698

Summary: PDE classpath container not updated when plugins from jars.extra.classpath change
Product: [Eclipse Project] PDE Reporter: Markus Keller <markus.kell.r>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: bsi.msa, curtis.windatt.public, Michael_Rennie, Olivier_Thomann
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Attachments:
Description Flags
project set none

Description Markus Keller CLA 2011-02-09 07:00:13 EST
Created attachment 188579 [details]
project set

I20110208-0800

The PDE classpath container is not updated when plugins from jars.extra.classpath change. Steps:

- new workspace
- import the attached team project set
=> compiles fine, only errors are missing EE and API Baseline

- close project org.apache.ant
=> invalid problems because PDE classpath container doesn't update correctly:

* The container 'Plug-in Dependencies' references non existing library '/org.apache.ant/lib/ant.jar'	org.eclipse.ant.core
* The project cannot be built until build path errors are resolved	org.eclipse.ant.core
* The project was not built since it depends on org.eclipse.ant.core, which has build path errors	org.eclipse.ant.launching
* The project was not built since it depends on org.eclipse.ant.core, which has build path errors	org.eclipse.ant.ui


=> Project > Clean... doesn't help.
=> Not even a restart helps. (Restart does help if you only have org.apache.ant and org.eclipse.ant.core in the workspace).

Only reliable remedy I found is to close/reopen/clean the org.eclipse.ant.* projects.
Comment 1 Eclipse Genie CLA 2019-09-07 17:23:17 EDT
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.