Summary: | [jar exporter] DCR: JAR Packager (1GCQCPV) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | enhancement | ||
Priority: | P4 | CC: | ronalbury |
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Windows NT | ||
Whiteboard: |
Description
Dani Megert
2001-10-10 22:57:56 EDT
- make sub-progressmonitor for export of multiple JARs This is now a separate PR and has P2: Jarpackager: progress reporting not optimal (http://dev.eclipse.org/bugs/show_bug.cgi?id=5853) Fixed: make sub-progressmonitor for export of multiple JARs (http://dev.eclipse.org/bugs/show_bug.cgi?id=5853) The remaining issues are: - remove usage of internal class (see above for more details) - create an ANT task that uses an existing jardesc file to export to a JAR - move all model tests to JarPackage and improve error messages - move strings to interface (constants) There is now a separate bug report for the .jardesc to ANT conversion (bug 28898). The remaining issues for this PR are: - remove usage of internal class (see above for more details) - move all model tests to JarPackage and improve error messages - move strings to interface (constants) Reassigning to inbox since there are currently no plans to work on this. I can't find the reference to an internal class. Closing, remaining items are minor. No - the remaining items are not minor. The rest of the world uses Ant. Eclipse will generate Ant scripts for most things we are trying to do in Java (compile, executable jar file, etc). Why did you deviate from Ant to create this jardesc file when you could have just had an Ant script do it ... and if you really want a jardesc file then at least provide an Ant task that can take the jardesc and create the Jar file. |