Ahh, now things are starting to work - very neat indeed! The current packaging with mvn install produces a .jar file, not sure if that is good, since it is not executable by java, so maybe .zip would be better?
With integration to PaxConstruct this would be really handy to package projects. Nice work! /peter http://www.oredev.se - Be there or be gone. GTalk: neubauer.peter Skype peter.neubauer ICQ 18762544 Phone +46704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - New Energy for Data - the Graph Database. http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. On Thu, Nov 13, 2008 at 3:08 PM, Thomas Joseph <[EMAIL PROTECTED]> wrote: > > > On Thu, Nov 13, 2008 at 7:23 PM, Peter Neubauer <[EMAIL PROTECTED]> > wrote: >> >> 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? > > Sure I will try to give. > >> >> 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? > > No, actually the packaging should have done the job. I did not double check > the artifact (Urrrgh!). I was directly working on the repository directory > structure (sort of war:inplace). I will try to fix it and give out a sample > too sooner. >> >> >> 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 > > > > -- > -- > Thanks and Regards, > > Thomas Joseph > ------------------------------------------------------------ > Promote Open Source - Promote Liberty of Ideas and Software. > ------------------------------------------------------------ > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
