Bug 21901 - JavaCore.setClasspathContainer is not generic enough
Summary: JavaCore.setClasspathContainer is not generic enough
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 2.1 M2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-25 09:17 EDT by Frank Cornelissen CLA
Modified: 2002-10-11 11:32 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Cornelissen CLA 2002-07-25 09:17:15 EDT
The above method seems to be the only way to propagate a change in the
resolution of container entries. 

However, it assumes that there is only *one* container entry per project. I want
to add several containers to a project, so i would have to call this method
several times, which can be very intensive (recompiling of the project etc)

Is there any other way to convince the javacore or a javaproject that the
contents of a container entry has changed?
Comment 1 Philipe Mulet CLA 2002-07-25 09:19:52 EDT
No. It can change one container setting for multiple projects at once, but only 
one container.

What you would need is a new API allowing you to perform multiple changes at 
once. Note that down the road, we want to provide a way to perform a bunch of 
operation as one (batched operation). This might be good enough to achieve what 
you need.
Comment 2 Philipe Mulet CLA 2002-10-08 09:07:44 EDT
Frank - now that you have the batching support (JavaCore.run
(IWorkspaceRunnable)), is it ok to close ?
Comment 3 Philipe Mulet CLA 2002-10-11 11:32:48 EDT
Closing, please reopen if you have more insights.