Community
Participate
Working Groups
NOTES: DM (5/22/01 6:21:40 PM) Released first version of JAR packager to 0.110 Open issues are: - create an ANT task that uses an existing jardesc file to export to a JAR - make sub-progressmonitor for export of multiple JARs - move all model tests to JarPackage and improve error messages - move strings to interface (constants) - remove usage of internal class (not a high prio item according to EG) SHOULD USE ANOTHER IMPL: 4.7.2 SourceFile Attribute The SourceFile attribute is an OPTIONALl fixed-length attribute in the attributes table of the ClassFile (ยง4.1) structure. There can be no more than one SourceFile attribute in the attributes table of a given ClassFile structure. The SourceFile attribute has the format SourceFile_attribute { u2 attribute_name_index; u4 attribute_length; u2 sourcefile_index; DM (5/22/01 7:47:58 PM) Fixed/Added: - what happens with a "normal" project? ==> we don't consider non-java projects (will be filtered out) - package list shows folder if folder is on classpath ==> fixed DM (5/23/01 11:49:55 AM) Fixed/Added: - error message if a file has compile errors ==> will be reported at the end (class file exported anyway) ==> can be configured via flags in the JarPackage (no UI yet) DM (5/23/01 1:27:13 PM) Fixed/Added: - append '.jardesc' as it is done with '.jar' - ensure that output folder == project works - warning if a file is being changed in the editor DM (5/25/01 11:49:56 AM) Changed: - source selection must be replaced with packages view DM (5/29/01 4:15:21 PM) Added: - created object contribution to re-generate a JAR based on a .jardesc file - created object contribution that allows to open the wizard on a .jardesc file DM (5/30/01 5:00:59 PM) Looked at: - show warning icon if there were only warnings ==> can't set icon on ErrorDialog and there's no WarningDialog for IStatus - close export wizard if there were only warnings DM (5/31/01 8:10:38 PM) Add/fixed: - make JAR export work with resources - test if .java file is on classpath if so select its cu - generate and read jardesc as XML (save i.e. can handle new and deleted attributes) EG (6/4/2001 12:38:20 AM) remaining open issues are deferred
- 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.