Hi, Am Montag, den 07.02.2011, 18:22 +0000 schrieb Sahoo: > On Monday 07 February 2011 11:00 PM, Stuart McCulloch wrote: > > > >> Since I can't use Export-Package: ...; version=${project.version}, is there > >> a variable/macro available to get the old behavior? > >> > >> > > <Export-Package>{local-packages};version="${project.version}"</Export-Package> > > > > > I didn't know I could actually use ${project.version}. Is this a recent > change in the plugin that it converts maven version to OSGi version? > Anyway, the suggestion worked.
This has long been implemented in the bundle plugin (there is an version-osgi-fier). What you also could do is to add packageinfo files listing the exported package's version. This is interpreted by the bnd library if present and valid. I wonder, whether other attributes and/or directives for an exported package could also be listed there ? (sorry for hijacking). Regards Felix > > is probably what you want - you'll need to run the manifest after the > > compilation phase because it now scans the output directory for the packages > > instead of the source directory (see > > https://issues.apache.org/jira/browse/FELIX-2808) > > > Yes, my pom is already set up to run manifest goal in process-classes phase. > > Thanks again, > Sahoo > > --------------------------------------------------------------------- > 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