[
https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011289#comment-13011289
]
David Jencks commented on KARAF-222:
------------------------------------
I'd like a description of exactly what you want this goal to do, I don't know
what jetty:run does.
As part of geronimo migration I have a base mojo that starts "karaf" as
described by a startup.properties file using aether to locate the listed
bundles (in the local maven repo). It would be easy (and I'll probably have to
do this for geronimo) to also deploy all the bundles listed as maven
dependencies. I imagine that the target/classes directory could also be
deployed as a bundle.
At the moment with the geronimo plugin you basically get the karaf command line
console showing after karaf startup. (in geronimo I shut it down again after
the plugin's work is performed).
> 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
>
> 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
