[jira] Commented: (KARAF-222) mvn karaf:run plugin, like jetty:run

["Andreas Pieber (JIRA)" <ji...@apache.org>]

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

Andreas Pieber commented on KARAF-222:
--------------------------------------

I've implemented some idea how this can look like here 

https://github.com/openengsb/openengsb/blob/master/tooling/maven-openengsb-plugin/src/main/java/org/openengsb/tooling/pluginsuite/openengsbplugin/Provision.java

Nevertheless I think this code will fit better directly in Karaf. Basically you can do a openengsb:run which scans all pom files for a configuration looking like:

{code}
<plugin>
        <groupId>org.openengsb.tooling.pluginsuite</groupId>
        <artifactId>maven-openengsb-plugin</artifactId>
        <version>${project.version}</version>
        <configuration>
          <provisionArchivePathUnix>${project.basedir}/target/openengsb-${project.version}.tar.gz</provisionArchivePathUnix>
          <provisionExecutionPathUnix>bin/openengsb</provisionExecutionPathUnix>
          <provisionArchivePathWindows>${project.basedir}/target/openengsb-${project.version}.zip</provisionArchivePathWindows>
          <provisionExecutionPathWindows>bin/openengsb.bat</provisionExecutionPathWindows>
        </configuration>
      </plugin>
{code}

In addition I think an variable to set environment vars such as KARAF_OPTS or KARAF_DEBUG would be nice. I mean this is far away from what is described in this issue, but at least it is an start. If you like the idea I can backport the code to Karaf...

WDYT?


> 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.
-
You can reply to this email to add a comment to the issue online.