karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-222) mvn karaf:run plugin, like jetty:run
Date Fri, 25 Mar 2011 13:38:05 GMT

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

james strachan commented on KARAF-222:

I still love the idea of the 'mvn karaf:run' goal - particularly the continuous watching &
rebuilding of the bundle like jetty:run does etc.

Just an aside that if folks want to deploy a jar/war/bundle/xml file into karaf (or tomcat/jetty
too) there's a mvn plugin I hacked up here...

which will provision the deployment unit (e.g. the bundle / war) into the deploy directory
of the application server you configure.

Though a karaf specific version of jetty:run would rock; we'd maybe be able to use the 'expanded
bundle' approach in Karaf - so rather than repeatedly copying classes & files into a jar,
we'd just make sure that everything is continuously compiled into target/classes and we add
a symlink of sorts in Karaf so it auto-reloads whenever we rebuild the code (or copy new config
files into the expanded bundle)

> 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

View raw message