Community
Participate
Working Groups
Open this bug after having fixed bug 97524. It appears that JDT/UI uses a dummy project to store and retrieve user libraries information. This currently has bad side effect mainly due to the fact that this dummy project neither exist in workspace nor has Java nature! JavaModelManager is not designed to work with such project and this is currently a source of potential bugs... JDT/Core has to provide API methods to allow its client to store and retrieve user libraries information in a safer way...
Of course post 3.1
Reopen for 3.2
Deferred post 3.2 as M5 is API freeze
Reopen as LATER is deprecated...
+1 It should be a legal way to add/change/remove user library information. Currently UserLibraryManager userLibraryManager = JavaModelManager.getUserLibraryManager(); userLibraryManager.setUserLibrary(libName, entries, isSystemLibrary); requires '@SuppressWarnings("restriction")' and sometimes generates nasty side effects.
Tentatively targeting 4.4
Too busy with Java 8 maintenance work - retargetting for 4.5
Crossed the time limit for API changes. moving to 4.6
I could look at this for M6, but considering that there's none pushing for it, I am taking it off the radar.