Community
Participate
Working Groups
Configurator tool should be able to get its program arguments from a java properties file. This will be an additional way to pass program arguments to the configurator tool. This is useful for the use cases where you can pass only one program argument during start.
+1 I maintain a command-line application with publisher, mirror, director and most of the p2.repository.tools that we use for our internal builds [1]. We also use this app for provisioning our production runtimes and our development environment (when target platforms are not enough). The command-line supports the argument "-props URL-OR-relative-URI-of-properties-file" [1] https://github.com/intalio/org.eclipse.equinox.p2.director.extended Inside the properties file, system properties are evaluated using the synthax ${sysprop} or ${sysprop,defaultvalue} The sysprop 'this.properties.server' is the base URL for the current properties file: With -props http://download.eclipse.org/jetty/updates/jetty-rt-3.7milestones/rtwebstarterkit.properties ${this.properties.server} -> http://download.eclipse.org The sysprop 'this.properties.parenturl' -> http://download.eclipse.org/jetty/updates/jetty-rt-3.7milestones Arguments passed on the command line override the ones in the properties file. For example: p2director -roaming -props http://download.eclipse.org/jetty/updates/jetty-rt-3.7milestones/rtwebstarterkit.properties Would make a roaming install of the EclipseRTWebStarterKit in the current directory. Let me know if you need volunteers to support this type of things.
