[
https://issues.apache.org/jira/browse/KARAF-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-26.
----------------------------------
Fix Version/s: 2.2.0
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/karaf/trunk ...
M main/pom.xml
M main/src/main/java/org/apache/karaf/main/Main.java
M main/src/main/java/org/apache/karaf/main/Utils.java
A shell/dev/src/main/java/org/apache/karaf/shell/dev/Restart.java
M shell/dev/src/main/resources/OSGI-INF/blueprint/shell-dev.xml
Committed r991865
> have restart clean command/API
> ------------------------------
>
> Key: KARAF-26
> URL: https://issues.apache.org/jira/browse/KARAF-26
> Project: Karaf
> Issue Type: New Feature
> Reporter: james strachan
> Assignee: Guillaume Nodet
> Fix For: 2.2.0
>
>
> in development its very common to want to trash the data directory, stop
> karaf then start again. Its kinda painful.
> it'd be good to do this in a single command.
> {code}
> restart:clean
> {code}
> which would move the ./data directory somewhere (into an old directory, maybe
> numbered so you've a history of logs etc) and then doing a
> System.exit(something) such that the shell script knows its a restart, where
> the shell script could then restart the JVM again.
> I can imagine this being useful in distributed testing/production uses where
> you want to basically restart a server from scratch so it might fetch new
> bundles on startup etc (without worrying about old stuff being stuck in the
> JVM).
> I guess restarting is one thing - and restarting clean (with the data
> directory going) is a secondary optional extra
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
