Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/532.2 (KHTML, like Gecko) Chrome/4.0.222.12 Safari/532.2 Build Identifier: 20090920-1017 JarPackageData and JarFileExportOperation classes are internal ones and wired to UI. This is why there is no way to export java project to a jar programatically. I think this should be separated. Reproducible: Always
Is anybody living here ? :)
To make it "visible" I changed to major
(In reply to comment #0) > JarPackageData and JarFileExportOperation classes are internal ones and wired > to UI. JarPackageData is API, it allows you to create an IJarBuilder, which in turn can be used to do all kinds of things. So what functionality do you see missing in the API? If you want to receive feedback from the authors of those classes, you should probably move this bug to the UI component. There really isn't much JDT/Core code involved in that. And: it still is a request for enhancement, isn't it?
Thanks for answer Stephan, Yes, this is enhancement. The main problem is, that jar export is in ui package as you said. If someone want to export a jar in headless mode (from a "headless" plugin without having workbench and GUI), then there is no way, since this plugin will require a lot of other plugins related to UI. This is the problem. I moved to UI, but anyway the problem is that this functionality should be moved to core from UI, so this bug can be in any project of the two.
> I moved to UI You actually moved it "between" Core and UI, since the assignee is still the jdt-core-inbox. Putting back to Core. This could be done in principle, but someone would have to provide a fully functional and non-breaking patch that moves the implementation to Core, keeps the API in UI stable and makes the UI use the code from Core (just duplicating the implementation is a no-go). JDT/UI currently does not have the resources to do that.
