Home » Eclipse Projects » Buckminster dev » [buckminster-dev] syntax of buckminster import command
|
| Re: [buckminster-dev] syntax of buckminster import command [message #485806 is a reply to message #485803] |
Tue, 15 September 2009 07:02   |
|
Hi Ted,
The importtargetdefinition and import are two different commands. The former imports an Eclipse Target Definition (i.e.
a .target file) and the latter imports a Buckminster CQUERY, BOM, or MSPEC.
Regards,
Thomas Hallgren
On 09/15/2009 08:46 AM, Ted Kubaska wrote:
> Reading 0.6 ... page 211 ... syntax of import command ...why is it not
> the same that I see on command line.
>
> Book:
> importtargetdefinition [ { -? | --help } ]
> [ { -A | --active } ]
> «url or path»
>
> Command LIne:
> tomcat> ./buckminster import --help
> Missing BOM URL
> Help text for org.eclipse.buckminster.core.import:This command will
> populate the workspace from a Bill of Materials (BOM)
>
> usage: import
> [{ -? | --help }]
> [{ -C | --continueonerror}]
> [{ -T | --template }<template workspace> ]
> <url_or_path>
>
> .......... details also show a -D, -B, -P, and -N
|
|
|
| Re: [buckminster-dev] syntax of buckminster import command [message #485961 is a reply to message #485803] |
Tue, 15 September 2009 17:16 |
 Ted Kubaska
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
Thanks ... the import I see with the --help on the command line ...
is this then the import (resolve) on page 206.
import [ { -? | --help } ]
[ { -B | --bomfile } «filename» ]
[ -C | --continueonerror ]
[ { -D | --define } «key» [ =«value» ] ]
[ { -P | --properties } «url or path» ]
[ { -t | --template } «template workspace» ]
«url or path»
which like the command line help has a -C but has a -t not a -T and
other options like -B, -D, and -P.
Bsically, trying to understand this line in one of our Hudson jobs
with the Buckminster plugin.
import ${WORKSPACE}/org.eclipse.ecf.platform.mspec
-ted
On Tue, Sep 15, 2009 at 12:02 AM, Thomas Hallgren <thomas@tada.se> wrote:
> Hi Ted,
> The importtargetdefinition and import are two different commands. The former
> imports an Eclipse Target Definition (i.e. a .target file) and the latter
> imports a Buckminster CQUERY, BOM, or MSPEC.
>
> Regards,
> Thomas Hallgren
>
>
> On 09/15/2009 08:46 AM, Ted Kubaska wrote:
>>
>> Reading 0.6 ... page 211 ... syntax of import command ...why is it not
>> the same that I see on command line.
>>
>> Book:
>> importtargetdefinition [ { -? | --help } ]
>> [ { -A | --active } ]
>> «url or path»
>>
>> Command LIne:
>> tomcat> ./buckminster import --help
>> Missing BOM URL
>> Help text for org.eclipse.buckminster.core.import:This command will
>> populate the workspace from a Bill of Materials (BOM)
>>
>> usage: import
>> [{ -? | --help }]
>> [{ -C | --continueonerror}]
>> [{ -T | --template }<template workspace> ]
>> <url_or_path>
>>
>> .......... details also show a -D, -B, -P, and -N
>
>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
--
-Ted
|
|
|
| Re: [buckminster-dev] syntax of buckminster import command [message #486099 is a reply to message #485961] |
Wed, 16 September 2009 10:58 |
Johannes Utzig
Messages: 329
Registered: July 2009 |
Senior Member |
|
|
Hi Ted,
I'm not sure I understand your question. This will simply start the
import operation (as described in the Bucky Book on the page you
mentioned) on the given mspec in the root of the workspace of the hudson
job.
Best regards,
Johannes
Ted Kubaska schrieb:
> Thanks ... the import I see with the --help on the command line ...
>
> is this then the import (resolve) on page 206.
>
> import [ { -? | --help } ]
> [ { -B | --bomfile } «filename» ]
> [ -C | --continueonerror ]
> [ { -D | --define } «key» [ =«value» ] ]
> [ { -P | --properties } «url or path» ]
> [ { -t | --template } «template workspace» ]
> «url or path»
>
> which like the command line help has a -C but has a -t not a -T and
> other options like -B, -D, and -P.
>
> Bsically, trying to understand this line in one of our Hudson jobs
> with the Buckminster plugin.
> import ${WORKSPACE}/org.eclipse.ecf.platform.mspec
>
> -ted
>
> On Tue, Sep 15, 2009 at 12:02 AM, Thomas Hallgren <thomas@tada.se> wrote:
>> Hi Ted,
>> The importtargetdefinition and import are two different commands. The former
>> imports an Eclipse Target Definition (i.e. a .target file) and the latter
>> imports a Buckminster CQUERY, BOM, or MSPEC.
>>
>> Regards,
>> Thomas Hallgren
>>
>>
>> On 09/15/2009 08:46 AM, Ted Kubaska wrote:
>>> Reading 0.6 ... page 211 ... syntax of import command ...why is it not
>>> the same that I see on command line.
>>>
>>> Book:
>>> importtargetdefinition [ { -? | --help } ]
>>> [ { -A | --active } ]
>>> «url or path»
>>>
>>> Command LIne:
>>> tomcat> ./buckminster import --help
>>> Missing BOM URL
>>> Help text for org.eclipse.buckminster.core.import:This command will
>>> populate the workspace from a Bill of Materials (BOM)
>>>
>>> usage: import
>>> [{ -? | --help }]
>>> [{ -C | --continueonerror}]
>>> [{ -T | --template }<template workspace> ]
>>> <url_or_path>
>>>
>>> .......... details also show a -D, -B, -P, and -N
>>
>> _______________________________________________
>> buckminster-dev mailing list
>> buckminster-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>
>
>
>
|
|
|
| Re: [buckminster-dev] syntax of buckminster import command [message #486189 is a reply to message #486099] |
Wed, 16 September 2009 16:01 |
Ted Kubaska
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
Thanks. Sorry, Johannes, for the confusion .. I don't think this is
very important. What I was trying to point out was that
the description of import in the book shows options -?,-B, -C, -D. -P, and -t
the online help for import shows options -D, -P, -B, -C, -N, -T (-N is
extra) but its usage (which appears before the list of options) shows
only -?, -C, and -t (lower case as opposed to list details and book).
On Wed, Sep 16, 2009 at 3:58 AM, Johannes Utzig <mail@jutzig.de> wrote:
> Hi Ted,
>
> I'm not sure I understand your question. This will simply start the import
> operation (as described in the Bucky Book on the page you mentioned) on the
> given mspec in the root of the workspace of the hudson job.
>
> Best regards,
> Johannes
>
> Ted Kubaska schrieb:
>>
>> Thanks ... the import I see with the --help on the command line ...
>>
>> is this then the import (resolve) on page 206.
>>
>> import [ { -? | --help } ]
>> [ { -B | --bomfile } «filename» ]
>> [ -C | --continueonerror ]
>> [ { -D | --define } «key» [ =«value» ] ]
>> [ { -P | --properties } «url or path» ]
>> [ { -t | --template } «template workspace» ]
>> «url or path»
>>
>> which like the command line help has a -C but has a -t not a -T and
>> other options like -B, -D, and -P.
>>
>> Bsically, trying to understand this line in one of our Hudson jobs
>> with the Buckminster plugin.
>> import ${WORKSPACE}/org.eclipse.ecf.platform.mspec
>>
>> -ted
>>
>> On Tue, Sep 15, 2009 at 12:02 AM, Thomas Hallgren <thomas@tada.se> wrote:
>>>
>>> Hi Ted,
>>> The importtargetdefinition and import are two different commands. The
>>> former
>>> imports an Eclipse Target Definition (i.e. a .target file) and the latter
>>> imports a Buckminster CQUERY, BOM, or MSPEC.
>>>
>>> Regards,
>>> Thomas Hallgren
>>>
>>>
>>> On 09/15/2009 08:46 AM, Ted Kubaska wrote:
>>>>
>>>> Reading 0.6 ... page 211 ... syntax of import command ...why is it not
>>>> the same that I see on command line.
>>>>
>>>> Book:
>>>> importtargetdefinition [ { -? | --help } ]
>>>> [ { -A | --active } ]
>>>> «url or path»
>>>>
>>>> Command LIne:
>>>> tomcat> ./buckminster import --help
>>>> Missing BOM URL
>>>> Help text for org.eclipse.buckminster.core.import:This command will
>>>> populate the workspace from a Bill of Materials (BOM)
>>>>
>>>> usage: import
>>>> [{ -? | --help }]
>>>> [{ -C | --continueonerror}]
>>>> [{ -T | --template }<template workspace> ]
>>>> <url_or_path>
>>>>
>>>> .......... details also show a -D, -B, -P, and -N
>>>
>>> _______________________________________________
>>> buckminster-dev mailing list
>>> buckminster-dev@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>>
>>
>>
>>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
--
-Ted
|
|
|
| Re: [buckminster-dev] syntax of buckminster import command [message #486217 is a reply to message #486189] |
Wed, 16 September 2009 18:59 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Greatful if this could be logged as a bugzilla issue against Buckminster
> Documentation so we can resolve where the issue is (the command, its
helpfile, or the book).
- henrik
Ted Kubaska wrote:
> Thanks. Sorry, Johannes, for the confusion .. I don't think this is
> very important. What I was trying to point out was that
>
> the description of import in the book shows options -?,-B, -C, -D. -P, and -t
> the online help for import shows options -D, -P, -B, -C, -N, -T (-N is
> extra) but its usage (which appears before the list of options) shows
> only -?, -C, and -t (lower case as opposed to list details and book).
>
|
|
|
Goto Forum:
Current Time: Tue Apr 16 22:06:08 GMT 2024
Powered by FUDForum. Page generated in 1.95559 seconds |
] 
Search
Help
Register
Login
Home
