Hi Christian,
As I know the context, I may have a different standpoint ;)
I would do the other way (it should be discussed on the Karaf mailing
list):
- the karaf-boot API define a "plugin" interface.
- each karaf-boot starter implement the interface to call what they want
(annotation processor, etc)
- the karaf-boot-maven-plugin is looking for the starters and load each
starter interface/code (by introspection)
WDYT ?
Regards
JB
On 04/26/2016 11:47 AM, Christian Schneider wrote:
I wonder if we could use classpath scanning to add bnd plugins to the
maven-bundle-plugin.
The background of this is that we are currently working on karaf boot.
The idea is to be able to
add some maven dependencies to your project like karaf-boot-starter-jpa
and auto enhance your project with
some dependencies as well as plugins to handle the specific technology.
The big problem is that maven does not allow to add maven plugins from
dependencies. So we are thinking about
using bnd plugins for our processing. This would work best if the
maven-bundle-plugin could auto detect bnd plugins
on the classpath. So the karaf boot starters would only need to contain
the plugins.
Does this make sense? Are there other ways to enhance a project with
kind of "aspects" like jpa support, cdi support or similar?
I know this all can be done with maven plugins but it results in big
poms that are not easy to start with.
Christian
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
