Affects Version/s: None
Fix Version/s: 1.0
Similar Issues:Show 10 results
MOP-42 Extend karaf command with ability to lauch karaf-client with a secondary command MOP-41 provide karaf command to explode and install karaf tarball before launching MOP-7 Provide good artifact management commands MOP-9 add uninstall <artifact> command MOP-10 add upgrade <artifact> command MOP-8 add install <artifact> command MOP-31 auto discover command classes with @Command annotations using packages in MOP; to avoid having to explicitly register all commands by hand & make it easy to auto-discover on the classpath MOP-13 it might be easier to develop commands if we had a simple annotated command-per-method way of coding them? MOP-36 need a way to pass command line arguments when running a Java main... MOP-11 add list [installed|all] command
we could do with an 'exec' which just executes the commands in a child process?
now we have fork, maybe we don't need "execjar" and "exec"?
names seem a bit inconsistent; we maybe need clearer names. e.g. fork, forkjar, forkrun maybe?
run - run java class
jar - run jar
exec - run arbitrary commands
then fork to fork a new jvm?
- fork <args>
- forkrun run a java class forked
- forkjar run a jar forked