I had a similar problem, maybe not the problem that you are having ...
Eclipse was insisting on having "osgi.bundle", not "osgi.bnd". So in my
compiled-bundle-settings pom.xml, I put:
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.0.0</version>
<configuration>
<instructions>
<Bundle-SymbolicName>${bundle.symbolicName}</Bundle-SymbolicName>
<Bundle-Version>${project.version}</Bundle-Version>
<Export-Package>!${bundle.namespace}.internal.*,
${bundle.namespace}.*;version="${project.version}"</Export-Package>
<Private-Package>${bundle.namespace}.internal.*</Private-Package>
<!--
PAX puts in the osgi.bnd, but Eclipse insists on having
osgi.bundle, so I moved over to osgi.bundle.... DCG 9/11/08
<_include>-osgi.bnd</_include>
-->
<_include>-osgi.bundle</_include>
</instructions>
</configuration>
</plugin>
This may help you,
Doug
On Mon, 2009-12-28 at 19:11 +0100, Andrea Polci wrote:
> I created a project using e2maven (Maven Project + Maven Module) and
> the archetypes maven-archetype-osgi-project and
> maven-archetype-osgi-bundle.
> All seems to work fine except that whatever i put in the osgi.bnd file
> in my bundle's project folter it dosen't affect at all the generated
> MANIFEST.MF.
>
> I tried with the "clean install" goals that cause the MANIFEST.MF to
> be regenerated but the content is always the same (the
> Bundle-Activator included in tbe osgi.bnd isn't present for example).
>
> I tried to create a similar project without eclipse from the maven
> command line and that way seems to work fine but don't understand what
> is the difference in the generated project that cause this beaviour.
>
> Can anyone help me?
>
> Thanks,
> Andrea
>
>
> --
> Andrea Polci
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
