felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-265) Empty line in a manifest
Date Fri, 30 Mar 2007 02:15:25 GMT

    [ https://issues.apache.org/jira/browse/FELIX-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485400

Stuart McCulloch commented on FELIX-265:

The manifest spec also states:

    "Groups of name-value pairs are known as a "section". Sections are separated from other
sections by empty lines."

    "The main section contains security and configuration information about the JAR file itself,
as well as the application or extension that this JAR file is a part of. It also defines main
attributes that apply to every individual manifest entry.  No attribute in this section can
have its name equal to  "Name". This section is terminated by an empty line."

If I read this correctly, the empty line in your example would mark the end of the main section
of the manifest (which  contains the OSGi metadata) and denotes the start of a new section
- the manifest parser would expect the new section to start with 'Name: <jar-entry>'
and any attributes would only apply to the named jar entry (btw, I don't believe entry-specific
OSGi metadata makes sense).

I hope this explains why the parsing stops at the new-line.

> Empty line in a manifest
> ------------------------
>                 Key: FELIX-265
>                 URL: https://issues.apache.org/jira/browse/FELIX-265
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>         Environment: Mac OS 10.4 and Java 1.4.2
>            Reporter: Charles Gouin-Vallerand
> When an empty line is add in a manifest file, the parsing of the manifest stop at the
empty line. Like in this example :
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.6.5
> Created-By: 1.4.2-70 ("Apple Computer, Inc.")
> Bundle-Name: IOEventCore
> Bundle-SymbolicName: IOEventCore
> Bundle-Version: 1.0.0
> Import-Package: ca.usherbrooke.domus.osgi.io.events.connection, 
>  ca.usherbrooke.domus.osgi.io.events.messages, ca.usherbrooke.
>  domus.osgi.io.events.module, ca.usherbrooke.domus.osgi.io.events.services, org.osgi.framework
> Bundle-Activator: ca.usherbrooke.domus.osgi.io.events.core.impl.IOCoreActivator
> In this example, the parsing stop after the "Created-By". The problem encountred in this
example is that the manifest is generated by ant with the concatenation of the 3 first lines
(automatically generated) and a text file containing the rest of the manifest.
> An empty line is authorized in the Java-Sun manifest standard : http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#JAR%20Manifest

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message