[
https://issues.apache.org/jira/browse/FELIX-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall closed FELIX-265.
---------------------------------
Resolution: Fixed
Assignee: Richard S. Hall
I guess this can be closed then...
> 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
> Assigned To: Richard S. Hall
>
> 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.
