You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/12/18 17:00:48 UTC
[jira] [Resolved] (KARAF-222) Provide karaf:run, karaf:deploy,
karaf:client Maven goals
[ https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-222.
----------------------------------------
Resolution: Fixed
> Provide karaf:run, karaf:deploy, karaf:client Maven goals
> ---------------------------------------------------------
>
> Key: KARAF-222
> URL: https://issues.apache.org/jira/browse/KARAF-222
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-tooling
> Reporter: james strachan
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)