Eclipse Community Forums: Buckminster » Without using an mspec, how do I materialize an osgi.bundle without binding it to my workspace

Home » Archived » Buckminster » Without using an mspec, how do I materialize an osgi.bundle without binding it to my workspace

Show: Today's Messages :: Show Polls :: Message Navigator

Without using an mspec, how do I materialize an osgi.bundle without binding it to my workspace [message #499691]

Mon, 23 November 2009 18:14

Corey Zimmet

Messages: 7
Registered: July 2009

Junior Member

I am a newbie to Buckminster and am having trouble bringing an existing
osgi.bundle component down into my workspace directory without it being
bound to hte workspace. I am able to do this with a mspec. However, I am
trying to establish a single cquery that can be run within eclipse that
requires no further action/thought on the developer's part to create a
workspac via an "Open a Componet Query" followed by a "Resolve and
Materialize".

I am guessing that it can be done with a buckminster bundle listing the
osgi.bundle as a prerequisite and using an svn fetcher. However, my
experiments show that the osgi.bundle will be brought down and bound.

Any pointers would be appreciated.

Thanks,
Corey

Report message to a moderator

Re: Without using an mspec, how do I materialize an osgi.bundle without binding it to my workspace [message #499724 is a reply to message #499691]

Mon, 23 November 2009 20:37

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

You can provide the mspec to the users, and they can import that. The
mspec can refer to the cquery.

- henrik

On 11/23/09 7:14 PM, Corey Zimmet wrote:
> I am a newbie to Buckminster and am having trouble bringing an existing
> osgi.bundle component down into my workspace directory without it being
> bound to hte workspace. I am able to do this with a mspec. However, I am
> trying to establish a single cquery that can be run within eclipse that
> requires no further action/thought on the developer's part to create a
> workspac via an "Open a Componet Query" followed by a "Resolve and
> Materialize".
>
> I am guessing that it can be done with a buckminster bundle listing the
> osgi.bundle as a prerequisite and using an svn fetcher. However, my
> experiments show that the osgi.bundle will be brought down and bound.
>
> Any pointers would be appreciated.
>
> Thanks,
> Corey
>
>
>

Report message to a moderator

Re: Without using an mspec, how do I materialize an osgi.bundle without binding it to my workspace [message #499904 is a reply to message #499724]

Tue, 24 November 2009 13:51

Corey Zimmet

Messages: 7
Registered: July 2009

Junior Member

Thanks for the help. I guess I am still looking for a way to do the
equivalent of a one click Import MSPEC without having to have any projects
already in the workspace.

Corey

"Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
news:heerpk$ost$1@build.eclipse.org...
> You can provide the mspec to the users, and they can import that. The
> mspec can refer to the cquery.
>
> - henrik
>
> On 11/23/09 7:14 PM, Corey Zimmet wrote:
>> I am a newbie to Buckminster and am having trouble bringing an existing
>> osgi.bundle component down into my workspace directory without it being
>> bound to hte workspace. I am able to do this with a mspec. However, I
>> am
>> trying to establish a single cquery that can be run within eclipse that
>> requires no further action/thought on the developer's part to create a
>> workspac via an "Open a Componet Query" followed by a "Resolve and
>> Materialize".
>>
>> I am guessing that it can be done with a buckminster bundle listing the
>> osgi.bundle as a prerequisite and using an svn fetcher. However, my
>> experiments show that the osgi.bundle will be brought down and bound.
>>
>> Any pointers would be appreciated.
>>
>> Thanks,
>> Corey
>>
>>
>>
>

Report message to a moderator

Re: Without using an mspec, how do I materialize an osgi.bundle without binding it to my workspace [message #499908 is a reply to message #499904]

Tue, 24 November 2009 14:03

Johannes Utzig

Messages: 329
Registered: July 2009

Senior Member

Corey Zimmet schrieb:
> Thanks for the help. I guess I am still looking for a way to do the
> equivalent of a one click Import MSPEC without having to have any projects
> already in the workspace.
>
> Corey
>

MSPECs work very similar to CQUERYs, so I don't quite understand your
problem. Instead of
File -> Open a component query -> enter a (remote) URL
you do
File -> Import -> Materialize from Buckminster MSPEC, CQUERY or BOM ->
enter a (remote) URL

It's one click more, but apart from that pretty much the same.

Best regards,
Johannes

Report message to a moderator

Re: Without using an mspec, how do I materialize an osgi.bundle without binding it to my workspace [message #499970 is a reply to message #499908]

Tue, 24 November 2009 15:14

Corey Zimmet

Messages: 7
Registered: July 2009

Junior Member

Thanks!

I didn't realize you could get to the Import MSPEC from the generic Import
option. I thought you could only get to the import MSPEC from the
Buckminster right click menu option on an existing MSPEC.

Thanks again,
Corey

"Johannes Utzig" <mail@jutzig.de> wrote in message
news:hegp4u$mli$1@build.eclipse.org...
> Corey Zimmet schrieb:
>> Thanks for the help. I guess I am still looking for a way to do the
>> equivalent of a one click Import MSPEC without having to have any
>> projects already in the workspace.
>>
>> Corey
>>
>
> MSPECs work very similar to CQUERYs, so I don't quite understand your
> problem. Instead of
> File -> Open a component query -> enter a (remote) URL
> you do
> File -> Import -> Materialize from Buckminster MSPEC, CQUERY or BOM ->
> enter a (remote) URL
>
> It's one click more, but apart from that pretty much the same.
>
>
> Best regards,
> Johannes

Report message to a moderator

Previous Topic:	Target platform vs. Buckminster headless installation
Next Topic:	[headless junit] pde junit support

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Jan 24 06:30:24 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter