felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dewire, Tom" <TDew...@ea.com>
Subject RE: Bug in maven-bundle-plugin?
Date Fri, 03 Aug 2007 14:25:15 GMT
Filed as Felix-333. Thanks!

--tom 

-----Original Message-----
From: mcculls@gmail.com [mailto:mcculls@gmail.com] On Behalf Of Stuart
McCulloch
Sent: Thursday, August 02, 2007 10:39 PM
To: dev@felix.apache.org
Subject: Re: Bug in maven-bundle-plugin?

On 03/08/07, Dewire, Tom <TDewire@ea.com> wrote:
> I'm using the 1.0.0 maven-bundle-plugin. It appears to be generating 
> an invalid manifest file when using the <Include-Resource> tag. More 
> specifically, it appears to not be stripping out the whitespace. 
> Placing the entire contents of the <Include-Resource> on one line 
> eliminates the problem.

Could you open an issue against the "Maven Bundle Plugin" component:

    http://issues.apache.org/jira/browse/FELIX

and attach both the pom.xml and generated manifest.

stripping whitespace could be done in the plugin before the directive is
passed to BND - or alternatively BND itself could handle directives with
spurious whitespace (this could benefit more users of BND).

tbtw, there is a users mailing list - you can subscribe over at:

    http://cwiki.apache.org/FELIX/mailinglists.html

but it doesn't have much traffic at the moment.

>
> Although I'm using felix for making the bundle, the target OSGI 
> implementation is Equinox.
>
> I apologize if using the "dev" list for this question is
inappropriate.
> I couldn't determine if there was also a "users" list (or something
> similar) in use. If so, I'd also love to get on it.
>
> --Tom DeWire
>
> A quick view of the generated manifest:
>
> === start ===
> Manifest-Version: 1.0
> Created-By: 1.5.0_06 (Sun Microsystems Inc.)
> Bundle-Activator: com.ea.nucleus.http.simple.probe.Activator
> Import-Package: com.ea.nucleus.configuration;version="[1,2)",com.ea.nu
>  cleus.http.simple.common;version="[2,3)",com.ea.nucleus.routing;versi
>  on="[1,3)",org.apache.commons.logging;version="[1.1,2)",org.osgi.fram
>  ework;version=1.3,simple.http;version=3.1.3
> Include-Resource: {src\main\resources},
>        @target\dependencies\sp
>  ring-core.jar,
>        @target\dependencies\spring-beans.jar,
>        @
>  target\dependencies\spring-context.jar,
>        @target\dependencies\c
>  onfiguration.spring.jar
> === lots more below here ===
>
> My plugin configuration looks like this:
>
> === lots more above here ===
>
> <!-- This will perform the actual bundling -->
>    <plugin>
>     <groupId>org.apache.felix</groupId>
>     <artifactId>maven-bundle-plugin</artifactId>
>     <version>1.0.0</version>
>     <extensions>true</extensions>
>     <configuration>
>      <instructions>
>       <Bundle-Name>${groupId}.${pom.artifactId}</Bundle-Name>
>
> <Bundle-SymbolicName>${groupId}.${pom.artifactId}</Bundle-SymbolicName
> >
>
> <Bundle-Activator>com.ea.nucleus.http.simple.probe.Activator</Bundle-A
> ct
> ivator>
>       <Import-Package>
>        org.osgi.framework,
>        org.apache.commons.logging;version="[1.1,2)",
>        com.ea.nucleus.configuration;version="[1,2)",
>        com.ea.nucleus.routing;version="[1,3)",
>        com.ea.nucleus.http.simple.common;version="[2,3)",
>        simple.http*;version="3.1.3",
>        !*
>       </Import-Package>
>       <Export-Package>
>        !*
>       </Export-Package>
>       <Private-Package>
>        com.ea.nucleus.http.simple.probe
>       </Private-Package>
>       <Include-Resource>
>        {src\main\resources},
>        @target\dependencies\spring-core.jar,
>        @target\dependencies\spring-beans.jar,
>        @target\dependencies\spring-context.jar,
>        @target\dependencies\configuration.spring.jar
>       </Include-Resource>
>      </instructions>
>     </configuration>
>    </plugin>
>
> === lots more below here ===
>


--
Cheers, Stuart

Mime
View raw message