Hi Thomas, On Thu, Nov 13, 2008 at 2:09 PM, Thomas Joseph <[EMAIL PROTECTED]> wrote: > I can foresee that I may end up writing a maven plugin to this effort. In > any case, what I aim is just a pre-requisite of Java to be there on the > target system. Yes, exactly, this is a different scope, a later stage native packaging plugin when Pax Packman has done its job of producing a nice Java package.
> > What I did was something cooked up in few hours, but now that I have my code > in the OPS4J repository, I expect some great minds to be there along... Any chance of just providing a simple example setup to e.g. package some PaxWicket or SpringDM or just basic PaxRunner assembly with the project which documents usage? I am trying to build the project with mvn install, then I unzipped the resulting artifact and try running start.sh. however, it seems PaxRunner has to be installed in the bin/paxrunner/bin dir? RUNNER_HOME=../ BASEDIR="$RUNNER_HOME" EXECUTABLE_DIR="$RUNNER_HOME"bin/pax*/bin So I naturally get an error there, [EMAIL PROTECTED] ~/c/code/ops4j/laboratory/open4thomas/pax-packman/target/bin $ ./start.sh ===================================== The following variables have been set ===================================== JAVA_OPTS = -Djava.util.Date=java.util.Date JAVA_HOME = C:\Program Files\Java\jdk1.6.0_03 CLASSPATH = RUNNER_ARGS = --args=file:../conf/runner.args Command Line Arguments = ===================================== Unable to access jarfile ../bin/pax*/bin//pax-runner-*.jar Should PaxRunner be prepackaged or installed during the boot process? Cheers /peter _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
