Michael McCallum wrote:
pomstrap could be used for the engine that launches the application
The appassembler does a bit more than just starting the application. It
has a rather big (and undocumented) contract with the environment. You
could start pomstrap with an appassembler-generated shell script.
strictly speaking you have no need to install much beyond a pom.xml, a
pomstrap jar and a batch/shell script to launch it. It then uses standard
maven2 resolution to build up the class path and run the defined
class/application.
You most definitely do. For one, you need integration into the
user/group permissions, memory settings and other stuff. The
appassembler also has handy small stuff like setting the basedir system
property making it very easy starting any java application from anywhere
on the system and not getting the files under the current directory.
you can bundle the pomstrap jar and the pom.xml into an executable jar
You could even start with a seed repository if you wanted to speed up the
first start up process.
Those two goals are itself useful for certain use cases, but the
original goal of appassembler was to be able to give java applications
an easy way to be started in a platform-depentent way, while giving the
application the same "write once, run everywhere" mantra back.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
