[ 
https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015789#comment-13015789
 ] 

David Jencks commented on KARAF-222:
------------------------------------

I'm assuming that everyone will be assembling their distributions using maven 
from kar files and features.  You can set up one kar file to have all the 
configuration info needed for a distro.  After doing this, including the kar 
file in your dependencies should give you the same "karaf" as unpacking the 
actual distribution, except without extracting all the bundles to the file 
system.  As I noted there are some problems in the diff, but it does show that 
it's possible to run "karaf" out of the maven repo in the same vm as maven and 
deploy maven dependencies as bundles ( I didn't check that feature and kar 
dependencies work yet).

I tried it by:

- adding to my ~/.m2/settings.xml:
    <pluginGroups>
        <pluginGroup>org.apache.karaf.tooling</pluginGroup>
    </pluginGroups>

- in a project that happens to build a bundle, do mvn karaf:run

There's way too much logging on the console, but karaf starts and you can use 
the console.
At the moment the project you run karaf in itself isn't deployed to karaf and I 
haven't thought about change listeners.

> mvn karaf:run plugin, like jetty:run
> ------------------------------------
>
>                 Key: KARAF-222
>                 URL: https://issues.apache.org/jira/browse/KARAF-222
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: james strachan
>         Attachments: KARAF-222-run-mojo-1.diff
>
>
> Did a quick google & couldn't see one yet - please close if there is one 
> already :)
> The really nice thing about jetty:run is it watches the source code & 
> target/classes dir & auto redeploys on change, so there's no deploy step - 
> you just hack & compile (which your IDE or incremental compile can do - e.g. 
> "mvn scala:cc").
> For added bonus would be being able to add some extra bundles, so it can be a 
> RAD way to hack bundles. Maybe folks could have some integration junit tests 
> automatically rerun whenever the bundle is redeployed?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to