Hi Paolo,
On Thu, 2011-04-07 at 02:31 +0100, Paolo Castagna wrote:
> Hi Dave,
> not being an OSGi expert, this is what I've tried to do at the time in the
> Jena
> pom.xml file:
>
> <profile>
> <id>OSGi</id>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.2</version>
> <configuration>
> <archive>
> <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
> </archive>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <extensions>true</extensions>
> <executions>
> <execution>
> <goals>
> <goal>manifest</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
> </profile>
>
> However, as far as I remember, there wasn't a great deal of feedback about it.
Not being a Maven person I don't understand what the profiles do or how
to invoke them or how that integrates with the rest of the build
process :)
However, presumably it would only create a jena.jar with a default
bundle manifest. I guess that's better than nothing but doesn't really
help that much. Rather than have to load all the Jena dependent jars in
as separate bundles it's more convenient to have a jena bundle that
includes them (or at least the ones that aren't likely to already be
present). Which is what the pom example I showed does, Clerezza's looks
very similar.
Dave
