Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Buckminster for Non-osgi projects(Buckminster for Non-osgi projects)
Buckminster for Non-osgi projects [message #804198] Wed, 22 February 2012 10:05 Go to next message
suman ravuri is currently offline suman ravuriFriend
Messages: 2
Registered: February 2012
Junior Member
Can we use Buckminster for Non OSGI projects?

Thanks,
Suman
Re: Buckminster for Non-osgi projects [message #804238 is a reply to message #804198] Wed, 22 February 2012 11:06 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
On 02/22/2012 11:05 AM, suman ravuri wrote:
> Can we use Buckminster for Non OSGI projects?
>
> Thanks,
> Suman

Yes, but you'll need to add cspecs to your projects and there is no build support provided out of the box.

- thomas
Re: Buckminster for Non-osgi projects [message #804927 is a reply to message #804238] Thu, 23 February 2012 06:34 Go to previous messageGo to next message
suman ravuri is currently offline suman ravuriFriend
Messages: 2
Registered: February 2012
Junior Member
Thanks for response.

Does it mean, we need to manually prepares .cspec or .cspecx files?

Thanks,
Suman
Re: Buckminster for Non-osgi projects [message #805064 is a reply to message #804927] Thu, 23 February 2012 09:44 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
On 02/23/2012 07:34 AM, suman ravuri wrote:
> Thanks for response.
>
> Does it mean, we need to manually prepares .cspec or .cspecx files?
>
> Thanks,
> Suman

Buckminster can be made to recognize your projects on one of two ways.

1. Use a buckminster.cspec file at the root of the project. This is the simplest approach.
2. Create an extension bundle for Buckminster that contains a component type/reader type combination that can make sense
of other files in the project and generate a cspec based on them. This bundle must then be installed into Buckminster.

Buckminster is bundled with extensions that makes it possible to use approach #2 for plug-ins, features, and maven
projects (contains a pom.xml).

- thomas
Re: Buckminster for Non-osgi projects [message #805291 is a reply to message #805064] Thu, 23 February 2012 15:37 Go to previous message
Henrik Lindberg is currently offline Henrik LindbergFriend
Messages: 2501
Registered: July 2009
Senior Member
In addition to what Thomas suggested - there is nothing preventing you
from using OSGi metadata even if you are never going to be running your
components in an OSGi container. i.e. "stick your stuff in a bundle".

- henrik

On 2012-23-02 10:44, Thomas Hallgren wrote:
> On 02/23/2012 07:34 AM, suman ravuri wrote:
>> Thanks for response.
>>
>> Does it mean, we need to manually prepares .cspec or .cspecx files?
>>
>> Thanks,
>> Suman
>
> Buckminster can be made to recognize your projects on one of two ways.
>
> 1. Use a buckminster.cspec file at the root of the project. This is the
> simplest approach.
> 2. Create an extension bundle for Buckminster that contains a component
> type/reader type combination that can make sense of other files in the
> project and generate a cspec based on them. This bundle must then be
> installed into Buckminster.
>
> Buckminster is bundled with extensions that makes it possible to use
> approach #2 for plug-ins, features, and maven projects (contains a
> pom.xml).
>
> - thomas
>
Previous Topic:hudson buckminster.json
Next Topic:Build eclipse project from ANT script
Goto Forum:
  


Current Time: Fri Dec 19 00:00:32 GMT 2014

Powered by FUDForum. Page generated in 0.12309 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software