[
http://issues.ops4j.org/browse/PAXRUNNER-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12334#action_12334
]
Mike Smoot commented on PAXRUNNER-177:
--------------------------------------
I've just committed code that adds a "script" executor. The idea is that
instead of actually running, shell and batch scripts get written to the runner
directory. This allows the runner directory to be zipped up and distributed as
a standalone application.
Run "pax-run.sh --executor=script" to generate the scripts.
Zipping and distribution are left to other tools.
> Create standalone executable instead of launching vm instantly
> --------------------------------------------------------------
>
> Key: PAXRUNNER-177
> URL: http://issues.ops4j.org/browse/PAXRUNNER-177
> Project: Pax Runner
> Issue Type: New Feature
> Components: frameworks
> Reporter: Toni Menzel
> Assignee: Alin Dreghiciu
>
> What we want:
> Have a target option for paxrunner that just works like we know it but
> instead of creating a new process with the new vm it should create a
> executable (jar) file that contains everything from the workingDir (all
> bundles+framework itself) and preserve all vm parameters.
> So this:
> # pax-run.sh --executor="bucket"
> should output a single jar in current directory called paxrunner-bucket.jar
> It can be run via:
> java -jar paxrunner-bucket.jar
> The filename can be set via option.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
