Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of mcculls@gmail.com designates
 209.85.216.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALhtWkdXwL-zHuvHBZ9jn59SctUC44KBP4-H0m4VvCgYbS1F8w@mail.gmail.com>
References: 
 <CALhtWkdXwL-zHuvHBZ9jn59SctUC44KBP4-H0m4VvCgYbS1F8w@mail.gmail.com>
Date: Sun, 28 Aug 2011 03:14:05 +0100
Message-ID: 
 <CAMr6Z4n=JLSu6rDK9ULZTRADaBK__P0LP3Xd3DuMfHdaZUzkjw@mail.gmail.com>
Subject: Re: generated manifest loses things on the way into the jar
From: Stuart McCulloch <mcculls@gmail.com>
To: users@felix.apache.org
Content-Type: multipart/alternative; boundary=0016e651f67439d07904ab875520

--0016e651f67439d07904ab875520
Content-Type: text/plain; charset=ISO-8859-1

On 28 August 2011 01:29, Benson Margulies <bimargulies@gmail.com> wrote:

> In my project, (using 2.3.5 and the bundle packaging) a perfectly
> reasonable manifest appears in target/classes/META-INF/MANIFEST.MF.
>
> However, the manifest that is actually delivered to the jar is
> DIFFERENT, and lacks a critical Export-Package.
>
> I don't know how to attack this.
>

I tried your example in FELIX-3091 and the export is there, but the last "t"
of the package is wrapped onto the next line. For some reason the manifest
extracted from the jar file has a different line-length wrapping than the
one written out to target/classes. But they do show the same packages when
you unwrap the content.

Note, you can use bnd to pretty-print the manifest which can help when
searching:

     java -jar bnd.jar print
target/org.apache.maven.doxia.eclipse.dependencies_1.0.0-SNAPSHOT.jar

See http://www.aqute.biz/Bnd/CommandLine http://www.aqute.biz/Bnd/Download

-- 
Cheers, Stuart

--0016e651f67439d07904ab875520--