Community
Participate
Working Groups
Overview: library support will define the concept of midlet suite library. a midlet suite project will be able to select the different libraries that it wants to use. once that happen, those libraries will be automatically added to the final midlet suite.
Hi all, i was studding possible solutions to this new feature and came up with some ideas: 1) The MTJ core will be updated to add: - Extension point were the implementer can define the new wireless library - A new Model for the the libraries; - A library manager to handle all implementations of the provided Ext. Point - ClasspathContainer handle to manage the libraries the user selected to be used in the project - update the project definition to add the library support 2) The MTJ UI will be updated to add: - new page in the New MIDlet Project Wizard, where the user can select the libraries (this page will be shown only if at least one lib is available) - new project page where the user can select/deselect the libraries to be used Notes: - The libraries will not be user editable. - Each new library will be composed for one or more jars. - Each library will have an individual Classpath Container Time frame: I believe I'll need something near to 3 or 4 weeks top to implement this feature, as such, we could add this to the 0.9.1 release.
Hi Diego, To get around this problem, I added a simple bit of code to the PreVerificationBuilder. (adds a copyExportedClassLibraries operation that is performed after the libraries have been preverified (if they are exported). Whilst this doesn't match your overview it seems to work well enough in my simple test scenarios. Would you be interested in a patch, if it achieves enough it could reduce your workload quite a bit.
There was a good chunk of this functionality in the EclipseME 0.7.9 release that may have been removed. It may be worth revisiting what I had in place regarding libraries in EclipseME. It may or may not be useful and will likely require work either way.
Hi Craig, I first tried using EclipseME, but with my configuration I didn't find it copied the exported jars into the newly created project jar; it was about this time that MTJ rebooted and so I tried with MTJ without success. The patch is quite trivial & so I'll attach a current patch once I have tested it against trunk (in a a day or so's time).
I've tested my implementation and it copies correctly the associated libraries to the final deployable jar. I've just had to used some JDT infrastructure. I have already commit the initial implementation for this feature. You can check it on the org.eclipse.mtj.core.library plug-in available in the SVN trunk. I believe I'll have an alpha implementation by the end of week.
The requirements may be found at the wiki: http://wiki.eclipse.org/DSDP/MTJ/Requirements/Library_Support
The requirements were update on the wiki pages.
bug released into 0.9.1
