Hi,
I'm currently trying to get used to the new enroute maven workspace
layout and now have some questions :)
1)
In a bnd workspace I had the central.xml file where I put all the
dependencies I wanted in my local maven bnd worspace repository. Where
do I put those dependencies now in the maven project workspace? In the
dependencies section of the root pom or rather in the dependencies
section of a specific module pom?
2)
In a bnd workspace I added the buildtime dependencies of a bundle to its
bnd file. What's the best practice now in a maven workspace? Do I add
those build time dependencies in the module pom?
3)
In Eclipse with bndtools installed and when using a bnd workspace layout
I am able to press the debug button of a bndrun file and everything is
perfectly integrated in the IDE. Additionally, when I change code of
bundles that are currently running in an osgi framework, then those are
rebuilt and redeployed on the fly.
Is there a way to reproduce a similar behavior only with maven commands
and a remote debugger?
Right now I'm following the enroute tutorial and every time I changed
something in the code I type the following commands:
1 mvn -pl app -am bnd-indexer:index bnd-indexer:index@test-index
bnd-resolver:resolve package
2 java -jar -Xdebug
-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=y
.\app\target\app.jar
3 Then I start my remote debugger to attach to the jvm
Are there other maven commands that would me allow to skip step 2 and 3?
Something like mvn jetty:run for web apps?
Kind regards,
Thomas
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
