Curious how folks doing OSGI work are doing their workflow with Maven.

OSGI is all about the modules and, typically, each module is its own
project.

I can see having a parent project with all of the modules, which makes it
easy to rebuild everything, but also wanting to just build the individual
modules.

But, also, in the generic NB workflow, you work on your project, and hit
Run and magic happens.

With OSGI, though, especially working with Karaf or even raw Felix, you
don't have an "application", you just have modules that are loaded into the
runtime.

And to get it to work, you have to copy all of the modules to the right
place, and then start Felix (or whatever), or at least reload the modules.

It just seems to me, out of the box, you kind of just give up things like
just click "Run" or "Debug" or any of the other runtime options.

Does anyone use custom maven goals to help with that? Do you just flip over
to a command line to run a script to gather everything up?

Just curious what the day to day life for OSGI under NB is like.

Thanks!

Regards,

Will Hartung

Reply via email to