Bugzilla – Full Text Bug Listing
| Summary: | [documentation] "launch" command should support running more than one .launch in parallel | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Thomas Hallgren <thomas> |
| Component: | Buckminster | Assignee: | buckminster.core-inbox <buckminster.core-inbox> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | bugs.eclipse.org, henrik.lindberg, thomas |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 319360 | ||
| Bug Blocks: | 319313 | ||
|
Description
Thomas Hallgren
Text incorporated in the documentation. Please note that the help file needs to be updated as the --ignoremissing option is not displayed in the 'usage' section. Actually. Achim changed the Launch.help some time after this bug was submitted. The --ignoremissing no longer exists and some texts have been updated. Here's the complete printout:
usage: launch
[{ -? | --help }]
[{-D | --define} <key>[=<value>]]
[{-P | --properties} <URL or Path>]
{-l | --launch} <workspace location of the launch config file>
[{--stdout}] [<path where stdout will be written to or "-" for passthrough>]]
[{--stderr}] [<path where stderr will be written to or "-" for passthrough>]]
-?
--help
Show this help text
-D
--define
Defines a property as a key=value pair. The value may include ant-style expansion constructs
that will be expanded using both System properties and other properties that has been set.
-P <URL or Path>
--properties <URL or Path>
The URL or file system path of a properties file. The values in the file may include ant-style
expansion constructs that will be expanded using both System properties and other properties
that has been set.
-l
--launch
The workspace location of the *.launch file that specifies the launch to run. If, for example,
your workspace contains a project named "com.acme.foobar" and this contains a launch
configuration named "my.launch", you would pass "com.acme.foobar/my.launch" as an
argument to the "-l" parameter.
--stdout
The path where the contents of the standard output stream of the launched process(es) will be
written to. Must point to a local file path. If empty, the content will be piped through
onto the regular standard output stream. The special value "-" (without quotes) may also
be used for that purpose.
NOTE: If you don't specify the --stdout parameter, the content will be swallowed.
--stderr
The path where the contents of the standard error stream of the launched process(es) will be
written to. Must point to a local file path. If empty, the content will be piped through
onto the regular standard error stream. The special value "-" (without quotes) may also
be used for that purpose.
NOTE: If you don't specify the --stderr parameter, the content will be swallowed.
(In reply to comment #2) > The --ignoremissing no longer exists and some texts have been updated. Here's > the complete printout: Why and what's the replacement? ECF build relies on --ignoremissing. This is a bit confusing and some additional documentation is needed.
There are two commands, launch and bglaunch. The latter is an extension of the first and it supports --ignoremissing. Here is the full printout for the bglaunch command.
This command launches a given launch configuration in the workspace in the background. The process
is taken down when the parent terminates.
usage: launch
[{ -? | --help }]
[{-D | --define} <key>[=<value>]]
[{-P | --properties} <URL or Path>]
[--ignoremissing]
{-l | --launch} <workspace location of the launch config file>
[{--stdout}] [<path where stdout will be written to or "-" for passthrough>]]
[{--stderr}] [<path where stderr will be written to or "-" for passthrough>]]
-?
--help
Show this help text
-D
--define
Defines a property as a key=value pair. The value may include ant-style expansion constructs
that will be expanded using both System properties and other properties that has been set.
-P <URL or Path>
--properties <URL or Path>
The URL or file system path of a properties file. The values in the file may include ant-style
expansion constructs that will be expanded using both System properties and other properties
that has been set.
-l
--launch
The workspace location of the *.launch file that specifies the launch to run. If, for example,
your workspace contains a project named "com.acme.foobar" and this contains a launch
configuration named "my.launch", you would pass "com.acme.foobar/my.launch" as an
argument to the "-l" parameter.
--stdout
The path where the contents of the standard output stream of the launched process(es) will be
written to. Must point to a local file path. If empty, the content will be piped through
onto the regular standard output stream. The special value "-" (without quotes) may also
be used for that purpose.
NOTE: If you don't specify the --stdout parameter, the content will be swallowed.
--stderr
The path where the contents of the standard error stream of the launched process(es) will be
written to. Must point to a local file path. If empty, the content will be piped through
onto the regular standard error stream. The special value "-" (without quotes) may also
be used for that purpose.
NOTE: If you don't specify the --stderr parameter, the content will be swallowed.
--ignoremissing
Iff the *.launch file specified by --launch cannot be resolved the background launch is silently
discarded.
|