|
|
|
|
| Re: Buckminster for Non-osgi projects [message #805291 is a reply to message #805064] |
Thu, 23 February 2012 10:37  |
Eclipse User |
|
|
|
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
>
|
|
|
Powered by
FUDForum. Page generated in 0.07016 seconds
Home