Hi. >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart >McCulloch >Sent: sexta-feira, 21 de Setembro de 2007 4:25 >To: [email protected] >Subject: Re: [Doubt] maven bundle plugin
>On 21/09/2007, Richard S. Hall <[EMAIL PROTECTED]> wrote: >> >> José Pacheco wrote: >> > Hello. >> > >> > >> > >> > I'm using the maven bundle plugin in a project and I need to set an >> > activator other them the bundle default one. >by default the bundle-plugin doesn't add a default Bundle-Activator entry >- it only adds one if there is a <Bundle-Activator>...</Bundle-Activator> >entry in the BND instructions in your POM >the deprecated osgi-plugin used to automatically try to detect the >activator, >but this can get complicated and it's better to be explicit and force >people >to >name the activator upfront so others looking at the sources know which one >is used. >> >> > Can I do this with the plugin? Is this a feature to be implemented in a >> new >> > version? >> >> I think you just need to manually specify the fully qualified class name >> of the activator. At this point in time, bundleplugin does not try to >> automatically detect the activator at all...at least as far as I know. >correct, see above >if you're using the maven-bundle-plugin and getting a Bundle-Activator >entry >then your project POM is probably inheriting BND instructions from another >POM in your project hierarchy. >if adding a <Bundle-Activator>...</Bundle-Activator> as shown in: > http://cwiki.apache.org/confluence/x/aX >doesn't help, then send me your POM and I'll take a look at what's >happening The problem is that I want to use an Activator from a project dependency, and when I package the project the maven-bundle-plugin tries to find the activator in the classpath of the bundle and it isn't there. This dependency will be available in the OSGI environment at runtime, and therefore not packaged with the bundle. >-> richard >> -- Cheers, Stuart
