fine by me. i assume the plugin will export every package?
-igor
On Fri, May 16, 2008 at 8:04 AM, Gerolf Seitz <[EMAIL PROTECTED]> wrote:
> hey,
>
> I was wondering whether we should follow the recent trend and include
> OSGi metadata with our releases?
> we could do this unobtrusively with the org.apache.felix:maven-bundle-plugin
> plugin.
> see the patch at the end of this mail.
>
> wdyt?
>
> Gerolf
>
>
>
>
> Index: pom.xml
> ===================================================================
> --- pom.xml (revision 650770)
> +++ pom.xml (working copy)
> @@ -545,6 +545,11 @@
> </execution>
> </executions>
> </plugin>
> + <plugin>
> + <groupId>org.apache.felix</groupId>
> + <artifactId>maven-bundle-plugin</artifactId>
> + <inherited>true</inherited>
> + </plugin>
> </plugins>
>
> <pluginManagement>
> @@ -615,6 +620,7 @@
>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> </manifest>
> +
> <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
> <manifestEntries>
> </manifestEntries>
> </archive>
> @@ -694,6 +700,19 @@
> </executions>
> <inherited>true</inherited>
> </plugin>
> + <plugin>
> + <groupId>org.apache.felix</groupId>
> + <artifactId>maven-bundle-plugin</artifactId>
> + <executions>
> + <execution>
> + <id>bundle-manifest</id>
> + <phase>process-classes</phase>
> + <goals>
> + <goal>manifest</goal>
> + </goals>
> + </execution>
> + </executions>
> + </plugin>
> </plugins>
> </pluginManagement>
> </build>
>
