Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 262768 - [jar exporter] Jardesc for normal Jar contains <fatjar builder="...
Summary: [jar exporter] Jardesc for normal Jar contains <fatjar builder="...
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.5 M6   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-28 10:16 EST by Markus Keller CLA
Modified: 2009-02-18 11:53 EST (History)
3 users (show)

See Also:
markus.kell.r: review+


Attachments
patch removing fatjar entry from jardesc files (5.25 KB, patch)
2009-02-07 15:15 EST, Ferenc Hechler CLA
markus.kell.r: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2009-01-28 10:16:52 EST
I20090127-2000

The *.jardesc generated from the normal JAR file exporter contains this line:

    <fatjar builder="org.eclipse.jdt.ui.plain_jar_builder" launchConfig=""/>

I don't see the benefit of this, especially since the Runnable JAR exporter does not support .jardesc files.
Comment 1 Markus Keller CLA 2009-01-28 11:13:33 EST
Benno or Ferenc, do you know more about this?
Comment 2 Ferenc Hechler CLA 2009-01-28 16:37:02 EST
In the beginning (bug 83258) the "Runnable Jar File Exporter" was planned to be an extension of the standard "Jar File Exporter". There was a select-box to choose the jar-builder which should be used to create the JAR.
Default was the PlainJarBuilder for normal jars, for runnable jars the FatJarBuilder could be selected. There also has been an ExtensionPoint for Plug-Ins to provide an own Builder and an implementation for the OneJarBuilder which provides a class-loader for Jar-in-Jar was written by me.

But then we decided to create an separate wizard for the "Runnable Jar File Exporter". The new Wizard should be easy to use and as this it is not very powerfull. For example, it is not possible to select or deselect single files which should be included or excluded. One of my ideas was to create a jardesc file from the "Runnable Jar File Exporter" and open it with the "Jar File Exporter", so that advanced users can customize their JARs.

But the jardesc files are not supported by the "Runnable Jar File Exporter" now. Instead of this ANT-Files can be generated which then can be customized.
So I see no need to support this entry (builder / launch_config) in the jardesc files any longer. 
When removing this entry we have to be compatible with old jardesc files which have an "fatjar" entry (class org.eclipse.jdt.internal.ui.jarpackager.JarPackageReader methode xmlReadFatjar).

I will have a look at this together with some other refactorings - today a lot of bugs where assigned to me  :) 




Comment 3 Benno Baumgartner CLA 2009-02-02 09:51:57 EST
Maybe we want to support jardescs for the runnable jar exporter in future versions? But until then I guess we can remove the builder id from the jardesc.
Comment 4 Ferenc Hechler CLA 2009-02-07 15:15:50 EST
Created attachment 125054 [details]
patch removing fatjar entry from jardesc files

The Patch removes the writing and reading of the fatjar entry when creating / opening jardesc files.
No special handling for reading is necessary, because unknown tags are simply ignored, nice!
Comment 5 Dani Megert CLA 2009-02-08 12:09:09 EST
>nice!
ok ;-)
Comment 6 Markus Keller CLA 2009-02-18 11:52:30 EST
Thanks, released to HEAD.