[
http://jira.amdatu.org/jira/browse/AMDATU-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11274#comment-11274
]
Bram de Kruijff commented on AMDATU-395:
----------------------------------------
Looks like at this point the ACE launcher will mostly suffice. The only thing
we need to do new is device a way to properly (re)package, document and
distribute it.
Initial thoughts:
1. Downloadable artifact
2. Usage documentation
3. Scripts (linux/windows)
4. Logging
Sample usage:
C:\bramk\Apache ACE\svn\ace-trunk\ace-launcher\target>java -jar
org.apache.ace.launcher-0.8.1-incubator-SNAPSHOT.jar help
Apache ACE Launcher
Usage:
java -jar ace-launcher.jar [identification=<id>] [discovery=<ace-server>]
[options...]
All known options are,
identification: sets the target ID to use
discovery: sets the ACE server to connect to
fwOption: sets framework options for the OSGi framework to be created. This
argument may be repeated
help: prints this help message
Example:
java -jar ace-launcher.jar identification=MyTarget
discovery=http://provisioning.company.com:8080
fwOption=org.osgi.framework.system.packages.extra=sun.misc,c
om.sun.management
> Create initial Amdatu launcher based on ACE
> -------------------------------------------
>
> Key: AMDATU-395
> URL: http://jira.amdatu.org/jira/browse/AMDATU-395
> Project: Amdatu
> Issue Type: Task
> Components: Amdatu Provisioning
> Affects Versions: 0.3.0-M0
> Reporter: Marcel Offermans
> Fix For: 0.3.0-M1
>
>
> We need a launcher that contains the Amdatu AMA and can be used to bootstrap
> a new target. Preferably this should be a single, executable JAR file that
> can be configured with a few command line options (to identify itself and to
> point to the Amdatu AMS).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers