Yes. That's what I thought. Just tried others too since documentation says $(maven-symbolicname).
Thanks. -----Original Message----- From: john.dun...@exceter.com [mailto:john.dun...@exceter.com] Sent: Friday, February 25, 2011 12:35 PM To: users@felix.apache.org Subject: RE: $(maven-symbolicname) property not working in maven bnd plugin In your pom, ${maven-symbolicname} would be the correct syntax. Whether or not a property of that name has actually been set is another matter. Quoting Raja Kannappan <rkannap...@axioma.com>: > I tried all possible combinations - $(maven-symbolicname), > ${maven-symbolicname), ${Bundle-SymbolicName), > $(bundle-symbolicname), ${bundle-symbolicname) and even > ${$(maven-symbolicname)} (because $(maven-symbolicname) was not > recognized as a property. So, I thought I would give this also a try). > > $(maven-symbolicname) and $(bundle-symbolicname) were not recognized > as a property and it came like that itself as a string in manifest. > Other things gave me null value. > > I checked out the code from here - > http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html and I > don't see anywhere where it sets the property value to project. > > Any ideas? > > > -----Original Message----- > From: Richard S. Hall [mailto:he...@ungoverned.org] > Sent: Friday, February 25, 2011 11:35 AM > To: users@felix.apache.org > Subject: Re: $(maven-symbolicname) property not working in maven bnd plugin > > Would it be $(bundle-symbolicname) ? > > On 2/25/11 11:32, john.dun...@exceter.com wrote: >> Are you using $(maven-symbolicname) or ${maven-symbolicname} ? >> >> Quoting Raja Kannappan <rkannap...@axioma.com>: >> >>> Hi, >>> >>> We use maven BND Plugin to generate OSGi bundles from regular jars. >>> We use it like this: >>> >>> <plugin> >>> <groupId>org.apache.felix</groupId> >>> <artifactId>maven-bundle-plugin</artifactId> >>> <configuration> >>> <instructions> >>> <Export-Package>com.mycompany.*</Export-Package> >>> </instructions> >>> </configuration> >>> <executions> >>> <execution> >>> <id>bundle-manifest</id> >>> <phase>process-classes</phase> >>> <goals> >>> <goal>manifest</goal> >>> </goals> >>> </execution> >>> </executions> >>> </plugin> >>> >>> As you can see this plugin is in process-classes phase. I've another >>> plugin execution happening at a later phase (verify) and it is >>> trying to read the property $(maven-symbolicname) generated by >>> bundle plugin. At least, that's what the documentation says - >>> http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html >>> >>> But, when I read that property I always get null. Does this property >>> work for anyone? Any ideas on what I'm missing here? >>> >>> Thanks, >>> >>> - Raja. >>> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org >> For additional commands, e-mail: users-h...@felix.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
