[
https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated KARAF-222:
-------------------------------
Attachment: KARAF-222-run-mojo-1.diff
I ported the geronimo stuff I had to karaf. There are a few odd bits:
-- at the moment I copied the needed files out of a karaf assembly into the
plugin. This is not OK for real usage, but there's a bit of chicken-egg
problem here since the obvious way to get these resources is by using the
karaf-maven-plugin which the run mojo is part of.
- I'm not sure how to offer the choice of felix/equinox since the classpath the
framework runs in is what is set up by maven. Maybe we should start the
framework in our own classloader that doesn't use the maven realm as parent.
Note that the "karaf" is started in the maven vm, not a separate vm. Is this a
problem?
> 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
