0

I would like to ask you some hints about the proper way to configure maven in the following scenario: I have some artifacts which are currently packaged as jar, but they have maven-bundle-plugin too because I want them become OSGI bundles, nevertheless I didn't change their package to bundle because it exists the case that I want build them as jar (or war sometimes).

To use maven-bundle-plugin with package jar I have followed this chapter and all worked fine, but now I'm considering to package them with bundle, to gain the full features of maven-bundle-plugin and because my default deploy is to OSGI.

So I would like to know if packaging artifacts as bundles but using them in a not OSGI container may results in troubles, what do you think? Thx

Gamby
  • 585
  • 1
  • 6
  • 22

1 Answers1

0

If you build your bundles using the alternative and newer plugin bnd-maven-plugin then it is not necessary to change the packaging type.

Neil Bartlett
  • 23,743
  • 4
  • 44
  • 77
  • Thanks, but it doesn't seem so much mature. And please are you able to answer my last question? – Gamby Jun 30 '17 at 08:08
  • 2
    The bnd-maven-plugin is mature and is used by many large organisations. What makes you think it's not mature? To answer your question: a bundle is a JAR file so yes of course you can use them outside OSGi. – Neil Bartlett Jun 30 '17 at 13:57
  • 1
    Can you please say why you think it is not mature? It has been available for several releases and is from the Bnd developers. – BJ Hargrave Jun 30 '17 at 14:13