[BLUEJ-266] Java ME library specification mechanism is too primitive
Java ME libraries are currently specified via the properties bluej.javame.corelibraries and bluej.javame.optlibraries with the former defaulting to "midpapi20.jar cldcapi11.jar" and the latter empty. BlueJ's usual library settings are ignored (on the grounds that they're probably for Java SE projects).
We need a better (i.e. GUI) way of specifying and checking Java ME-specific libraries, not least because the new Java ME SDK from Sun (3.0) has changed the names of the core libraries Jar files.
----
Interim fix implemented for 3.0.2: If the Jar files named in the corelibraries property don't exist, "sensible default" files are identified and written back into the property. This means that Java ME development will work out-of-the-box with any sensible emulator/toolkit package, without messing up any manual changes made by the user.
Issue metadata
- Issue type: Task
- Priority: Low
- Fix versions: 3.1.6