You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/12/18 16:58:47 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15064132#comment-15064132 ] 

ASF subversion and git services commented on KARAF-222:
-------------------------------------------------------

Commit 335620adb7b1cc92380ec9cba7eb2dbbaa8bb96c in karaf's branch refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=335620a ]

KARAF-222 - Provide karaf:run, karaf:deploy, karaf:client Maven goals


> 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é
>         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)