Eclipse Community Forums: Eclipse Platform » Missing META-INF folder in build result (eclipse SDK)

Home » Eclipse Projects » Eclipse Platform » Missing META-INF folder in build result (eclipse SDK)(META-INF folder is missing in the zip file after eclipse SDK build execution)

Show: Today's Messages :: Show Polls :: Message Navigator

Missing META-INF folder in build result (eclipse SDK) [message #527130]

Wed, 14 April 2010 08:13

Mitsuki Touno

Messages: 28
Registered: April 2010

Junior Member

Dear forum members,

Please let me know if I'm posting a duplicated topic, or posting a topic to a wrong forum. So far I haven't found any similar topic.

I'm building eclipse SDK by using build scripts in org.eclipse.releng.eclipsebuilder project. Source files are checked out from CVS repository and invoking build with buildFromSource.xml file. So far I used map files from eclipse 3.6 M3 and M6 version.

Now I'm getting the resulting zip file. I can run eclipse with extracted binary, but META-INF folders in feature folders are missing. If I check the folder structure of production version (eclipse-SDK-3.6M3-win32.zip or so), there are META-INF folder under each feature directory.

Here my question is, why I'm not getting META-INF folder in my build result?

==== Environment Info ====
Platform: Windows 7 professional / Windows XP Professional
Build methodology: org.eclipse.releng.eclipsebuilder
Source files: Fetched from eclipse CVS as per M3 / M6 map files
========

Thanks in advance and best regards,

Mitsuki Touno

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #527169 is a reply to message #527130]

Wed, 14 April 2010 10:29

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

Mitsuki,

Features don't typically have a META-INF folder... What's specified in
the build.properties for these things?

Mitsuki Touno wrote:
> Dear forum members,
> Please let me know if I'm posting a duplicated topic, or posting a
> topic to a wrong forum. So far I haven't found any similar topic.
> I'm building eclipse SDK by using build scripts in
> org.eclipse.releng.eclipsebuilder project. Source files are checked
> out from CVS repository and invoking build with buildFromSource.xml
> file. So far I used map files from eclipse 3.6 M3 and M6 version.
> Now I'm getting the resulting zip file. I can run eclipse with
> extracted binary, but META-INF folders in feature folders are missing.
> If I check the folder structure of production version
> (eclipse-SDK-3.6M3-win32.zip or so), there are META-INF folder under
> each feature directory.
> Here my question is, why I'm not getting META-INF folder in my build
> result?
> ==== Environment Info ====
> Platform: Windows 7 professional / Windows XP Professional
> Build methodology: org.eclipse.releng.eclipsebuilder
> Source files: Fetched from eclipse CVS as per M3 / M6 map files
> ========
>
> Thanks in advance and best regards,
>
> Mitsuki Touno
>
>
>

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #527344 is a reply to message #527169]

Wed, 14 April 2010 21:39

Mitsuki Touno

Messages: 28
Registered: April 2010

Junior Member

Dear Ed-san,

Thanks for your reply. Actually we have not modified any build.properties of features, so they are as they are in CVS repository.

For example, below is the entries of build.properties for org.eclipse.sdk feature.

BTW, there is META-INF folder in each feature folder of production version of eclipse SDK which I downloaded from eclipse download page. I need to generate completely same folder structure and same binaries.
Please let me know what is required to generate META-INF folder, if any specific configuration is necessary.

Thanks regards,

Mitsuki

==== FROM HERE ====
############################################################ ###################
# Copyright (c) 2000, 2009 IBM Corporation and others.
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#
# Contributors:
# IBM Corporation - initial API and implementation
############################################################ ###################
bin.includes=epl-v10.html,eclipse_update_120.jpg,feature.xml ,feature.properties,license.html

generate.feature@org.eclipse.platform.source=org.eclipse.platform,feature@org.eclipse.rcp.source,feature@org.eclipse.equinox.p2.user.ui.source;optional="true",plugin@org.eclipse.platform.doc.isv;unpack="false",\
plugin@org.apache.ant.source;version=1.7.1.qualifier;unpack="false",\
plugin@com.jcraft.jsch.source;version=0.1.41.qualifier;unpack="false",\
exclude@org.eclipse.platform.doc.user

generate.feature@org.eclipse.jdt.source=org.eclipse.jdt, plugin@org.eclipse.jdt.doc.isv;unpack="false",\
plugin@org.junit.source;version=3.8.2.qualifier;unpack="false",\
plugin@org.junit.source;version=4.8.1.qualifier;unpack="false",\
plugin@org.hamcrest.core.source;version=1.1.0.qualifier;unpack="false",\
exclude@org.eclipse.jdt.doc.user
generate.feature@org.eclipse.pde.source=org.eclipse.pde,plugin@org.objectweb.asm.source;version=3.2.0.qualifier;unpack="false",\exclude@org.eclipse.pde.doc.user
generate.feature@org.eclipse.pde.p2.source=org.eclipse.pde.p2
generate.feature@org.eclipse.cvs.source=org.eclipse.cvs
generate.feature@org.eclipse.help.source=org.eclipse.help,\
plugin@javax.servlet.source;version=2.5.0.qualifier;unpack="false",\
plugin@javax.servlet.jsp.source;version=2.0.0.qualifier;unpack="false",\
plugin@org.apache.jasper.source;version=5.5.17.qualifier;unpack="false",\
plugin@org.apache.commons.el.source;version=1.0.0.qualifier;unpack="false",\
plugin@org.apache.commons.logging.source;version=1.0.4.qualifier;unpack="false",\
plugin@org.apache.lucene.source;version=1.9.1.qualifier;unpack="false",\
plugin@org.apache.lucene.analysis.source;version=1.9.1.qualifier;unpack="false",\
plugin@org.mortbay.jetty.util.source;version=6.1.15.qualifier;unpack="false",\
plugin@org.mortbay.jetty.server.source;version=6.1.15.qualifier;unpack="false"

generatedVersionLength=45
==== TO HERE ====

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #527685 is a reply to message #527130]

Fri, 16 April 2010 06:49

Mitsuki Touno

Messages: 28
Registered: April 2010

Junior Member

Hi,

If anyone has idea about this, please let us know.

Thanks regards,

Mitsuki

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #527740 is a reply to message #527685]

Fri, 16 April 2010 10:14

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

This is a multi-part message in MIME format.
--------------050705050509050003050701
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Mitsuki,

It's not mentioned in the build.properties and if it's not in CVS, it
must be generated. From the comments one gets the impression that Ant
is being used to create it

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 2.3 (IBM Corporation)

It's not a bundle manifest like the ones that appears in bundles/plugins.

So I guess the underlying question is: what build script generates these
things? I'm not sure the release engineers for the platform read this
newsgroup/forum...

Mitsuki Touno wrote:
> Hi,
> If anyone has idea about this, please let us know.
> Thanks regards,
> Mitsuki
>

--------------050705050509050003050701
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Mitsuki, 
 
It's not mentioned in the build.properties and if it's not in CVS, it
must be generated. From the comments one gets the impression that Ant
is being used to create it 
<blockquote>Manifest-Version: 1.0 
Ant-Version: Apache Ant 1.7.1 
Created-By: 2.3 (IBM Corporation) 
</blockquote>
It's not a bundle manifest like the ones that appears in
bundles/plugins. 
 
So I guess the underlying question is: what build script generates
these things? I'm not sure the release engineers for the platform read
this newsgroup/forum... 
 
 
Mitsuki Touno wrote:
<blockquote cite="mid:hq91ae$vjp$1@build.eclipse.org" type="cite">Hi, 
If anyone has idea about this, please let us know. 
Thanks regards, 
Mitsuki 
 
</blockquote>
</body>
</html>

--------------050705050509050003050701--

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #528029 is a reply to message #527130]

Sun, 18 April 2010 22:39

Mitsuki Touno

Messages: 28
Registered: April 2010

Junior Member

Dear Ed-san,

Thanks for reply and my apologies for delayed response.
Actually I was not able to read any topic since 17th-Apr because forum server was unstable.

If you know which forum I should post my question, please let me know.

Thanks regards,

Mitsuki

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #528038 is a reply to message #527130]

Mon, 19 April 2010 04:41

Mitsuki Touno

Messages: 28
Registered: April 2010

Junior Member

I did some researches and found below things.

1. build.properties files from plugins include the value of "META-INF" in "bin.includes" section by default, but it is not there in build.properties files from features.

2. There are some logics included in GatherBundleTask.java, which deal with manifest file, but those are not there in GatherFeatureTask.java.

3. META-INF/MANIFEST.MF file is already there in the source folders of plugins when they are fetched from CVS. But this file is not included in features. Even META-INF folder is not there.

So far I could not find any task which generates manifest file. Whatever I found is the task which manages to include existing manifest file into each jar file.

Therefore I assume that we cannot generate manifest file nor include it to final build resut with build scripts provided as org.eclipse.releng.eclipsebuilder project.

I want to confirm this idea with any releng expert. Please let me know how I can ask this.

Thanks regards,

Mitsuki

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #528165 is a reply to message #528038]

Mon, 19 April 2010 15:01

Kim Moir

Messages: 39
Registered: July 2009

Member

Mitsuki,

Could you please open a bug under Eclipse->Platform->releng
for this issue describing the steps you took? I'm not sure what is causing your problem.

Kim
Eclipse and Equinox release engineering

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #528284 is a reply to message #527130]

Mon, 19 April 2010 22:47

Mitsuki Touno

Messages: 28
Registered: April 2010

Junior Member

Dear Kim-san,

Thank you very much for your response. I have raised a new bug report as 309748. I'm not sure if this is a defect or this is by specification.
Please check the same and if any info is missing or entered incorrectly, please kindly let me know.

Thanks regards,

Mitsuki

Report message to a moderator

Re: Missing META-INF folder in build result (eclipse SDK) [message #529162 is a reply to message #527130]

Fri, 23 April 2010 09:10

Mitsuki Touno

Messages: 28
Registered: April 2010

Junior Member

1 confirmation, should I get META-INF folder in my eclipse build file if everything is working fine, or META-INF folder is not generated with the build scripts provided by eclipse.org?

If META-INF is not generated by specification, then this is not a defect. So please let me know this particular point if anyone has idea.

Thanks regards,

Mitsuki

Report message to a moderator