[
https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015774#comment-13015774
]
David Jencks commented on KARAF-222:
------------------------------------
There are a lot of possible ways to have something like karaf:run. One of them
is certainly unpacking an actual karaf distro. What I did, unning a "karaf"
instance that only involves a few configuration files and takes all the bundles
from the local maven repo, ought to be a lot faster to start up since there's
basically no file copying.
I think this is a useful base for other kinds of mojos, and I need the base
functionality for a while in geronimo, so I'm going to be maintaining it
somewhere for a few months. If people are interested I can work more on fixing
problems, otherwise we can drop it.
I don't really understand what the difference between a profile and a kar file
is. A kar file can contain arbitrary content that ends up in the server,
features, bundles, configuration for the bundles.
> 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
