On Tue, Apr 5, 2016 at 11:00 PM, Matt Pavlovich <mattr...@gmail.com> wrote:
> I was ruminating about this as well-- I agree its not exact; however, is
> there any real impact? The bundle version is indicated by the SNAPSHOT.
> How would the package export having the .SNAPSHOT qualifier (which would
> not impact any wiring) have any undesirable impact?
>
Hmmm... To be frank, off the top of my head right now, I can't come up with
a scenario where one would want to run coexisting SNAPSHOT and FINAL
modules for the same version. But the fact that one doesn't come to mind
doesn't mean that it's ok to bypass semantic accuracy.
In fact, the bnd docs even recognise using qualifiers to designate build
specifiers in package exports. So right now it feels like a shortcoming/bug
of the bnd-maven-plugin.
If you now export the package (from any bundle that has the package on its
> class path), it will be properly versioned.
> bnd.bnd:
> build = ${tstamp}
> Export-Package: com.example.*
> The resulting manifest will look like:
> Manifest:
> Export-Package: com.example; version=1.2.0.*v201010101010*
http://www.aqute.biz/Bnd/Versioning
My conclusion is that changing our package export policy as a consequence
of a possible (temporary) bug in the bnd-maven-plugin doesn't seem a sound
approach IMHO.
My preference would be to open a bug upstream and send a PR to fix the
issue there.
Cheers,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
Blog: raul.io
<http://raul.io/?utm_source=email&utm_medium=email&utm_campaign=apache> |
twitter: @raulvk <https://twitter.com/raulvk>
