Bug 6846 - JAR exorter problems with META-INF
Summary: JAR exorter problems with META-INF
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 6890
Blocks:
  Show dependency tree
 
Reported: 2001-12-12 10:04 EST by Ray Elenteny CLA
Modified: 2002-02-13 06:21 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ray Elenteny CLA 2001-12-12 10:04:45 EST
I have a META-INF directory that is part of my source tree.  When I execute a 
build, the contents of the META-INF directory are correctly placed in the build 
directory.  However, when I choose to export to a JAR file, the META-INF 
directory is placed in a location relative to the path within my project.  For 
example, my source directory is located at /PROJECT/source/server/java.  Under 
this directory is a "com" directory and the META-INF directory.  When exported, 
the contents of the "com" directory are exported properly, but the path to the 
META-INF directory in the JAR file is prefixed with source/server/java.
Comment 1 Dani Megert CLA 2001-12-13 06:00:58 EST
Can't reproduce with current code (HEAD). What I see is
- "normal" resource folders are treated correclty i.e. a (resource) folder in 
your java directory would not contain the source folder path (note: there's an 
option to add that path anyway).
- "META-INF" is completely hidden since it is a special folder

Please provide more steps to repoduce (what build id, which exporter do you use, 
what are the settings you use...).
Comment 2 Ray Elenteny CLA 2001-12-13 07:08:12 EST
I'm sorry for not providing the build information.  I am using the 20011206 
build.  Per your email, I did not have a "normal" resource directory.  I went 
ahead and created one and was able to see the results you expected.  The 
resource folder is properly stored in the jar file.

You mention the META-INF is a special directory.  I agree, but I have created 
one in my project and included files in it to be a part of a jar file (i.e. ejb-
jar.xml).  It appears that there is some special handling of the META-INF 
directory going on, as you said.  How can I include files that should be a part 
of the META-INF directory?

The 1.0 stream did not exhibit this behavior.  I'm not saying that in order for 
you to change it back, but I just wanted to let you know that is how we had 
been using the JAR facility in the previous stream.

Thanks!
Comment 3 Dani Megert CLA 2001-12-13 07:49:40 EST
I have changed the title of the PR.

For now there's no way to achieve what you want with the JAR file exporter. I 
have filed a PR against Java core about hiding META-INF.

A possible workaround for you (since you already have the META-INF and hopefully 
the manifest file(s)) could be to use the Zip exporter: make a full build and 
then export the bin directory.
Comment 4 Ray Elenteny CLA 2001-12-13 08:48:52 EST
I have already tried the ZIP file workaround and it does work.  It's just a 
little more difficult to set it up.  However, it will work for now.

Thanks!
Comment 5 Dani Megert CLA 2001-12-17 06:04:12 EST
Moving to REMIND until JCore PR is fixed.

Comment 6 Dani Megert CLA 2002-01-23 10:49:32 EST
Verified against build 20020122 -> OK
Comment 7 Dani Megert CLA 2002-01-23 10:51:49 EST
Fixed and verified.
Comment 8 Dani Megert CLA 2002-01-23 10:52:46 EST
Want to get rid of "REMIND" flag
Comment 9 Dani Megert CLA 2002-01-23 10:53:12 EST
Need to get rid of REMIND
Comment 10 Dani Megert CLA 2002-01-23 10:56:44 EST
Fixed
Comment 11 Martin Aeschlimann CLA 2002-02-13 06:21:08 EST
Verified ->20020205. JRT.