The differences between JAR and SUBSYSTEM manifests are defined in the introduction of section 134.2:
The Subsystem and Deployment Manifest follow the JAR manifest format (version 1.0), but with the following relaxed rules: • No limit on the line length. Lines are allowed to exceed the JAR manifest maximum of 72 bytes. • The last line is not required to be a carriage-return new-line combination. • There is only one section in the manifest (the main section). A Subsystems implementation is free to ignore other sections of the manifest. Generally speaking, whitespace between paths, parameters, and their terminals should be ignored. Can you open a JIRA [1] and attach a manifest that you think should work? [1] https://issues.apache.org/jira/browse/ARIES On Fri, Oct 2, 2015 at 8:44 PM, Paul F Fraser <[email protected]> wrote: > The cmpn spec gives examples of Subsystem-Content > > Subsystem-Content: > org.acme.billing.impl; > type=osgi.bundle; > version=1.0, > etc... > using tabs or multiple spaces. > > Aries Subsystems depend on a single space as a line continuation, which I > think is a java manifest requirement. > > Should the spec not show the examples formatted with multiple spaces or > should Aries sub systems allow multiple spaces as line continuations? > > The requirement for single space line continuations had me baffled for quite > a while until I debugged into aries and discovered the single space > requirement. > > Regards > > Paul Fraser > >
