|
| Re: Making source features with Buckminster [message #487006 is a reply to message #486995] |
Mon, 21 September 2009 13:08   |
|
Hi Oisin,
Buckminster will generate source bundles and source features by default. You can turn it off by setting the property
cbi.include.source=false.
One thing to remember. In the manifest editor, there is a 'Build' tab. In that tab, you can select what you want
included in the 'Source Build'. You only need do check those things that are not normally included in the source. In
particular, you should *not* check things like the META-INF or the plugin.xml as they are generated in a source bundle.
Buckminster will create one source bundle per bundle and one specific source feature per feature. They will not be
categorized in the final site unless you do so explicitly.
If this isn't documented in the Bucky book, then that's an oversight that deserves a bugzilla.
Regards,
Thomas Hallgren
On 09/21/2009 02:51 PM, Oisin Hurley wrote:
> I've googled around for this and checked through the BuckyBook, but I
> didn't find anything particularly relevant. Is there a way to instruct
> Buckminster to add the source code of the plugins to a build? The idea
> is to make it easy to construct SDK bundles which contain source,
> examples, etc.
>
> There may be a simple way to do this that I have missed...
>
> cheers
> --oh
|
|
|
| Re: Making source features with Buckminster [message #487076 is a reply to message #487006] |
Mon, 21 September 2009 18:22 |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Bucky Book 0.6 (I think this was in 0.5 as well) has the following info
on page 154:
"cbi.include.source
Controls generation of source features and bundles. When set to true,
source bundles are generated and included in the update site.
Warning
Source features and bundles are generated and included in the update
site unless you set this property to false. For open source projects
this is typically what is wanted, but it may not be suitable for your
project."
I agree this is not in the most prominent of places (in the reference
page for the site.p2 action).
Maybe just include a "building source" section in the site building
example (to get a heading in the TOC) that shows the use of this
property (i.e. do nothing if you want the source bundles).
Wht do you think?
- henrik
Thomas Hallgren wrote:
> Hi Oisin,
> Buckminster will generate source bundles and source features by default.
> You can turn it off by setting the property cbi.include.source=false.
>
> One thing to remember. In the manifest editor, there is a 'Build' tab.
> In that tab, you can select what you want included in the 'Source
> Build'. You only need do check those things that are not normally
> included in the source. In particular, you should *not* check things
> like the META-INF or the plugin.xml as they are generated in a source
> bundle.
>
> Buckminster will create one source bundle per bundle and one specific
> source feature per feature. They will not be categorized in the final
> site unless you do so explicitly.
>
> If this isn't documented in the Bucky book, then that's an oversight
> that deserves a bugzilla.
>
> Regards,
> Thomas Hallgren
>
>
>
> On 09/21/2009 02:51 PM, Oisin Hurley wrote:
>> I've googled around for this and checked through the BuckyBook, but I
>> didn't find anything particularly relevant. Is there a way to instruct
>> Buckminster to add the source code of the plugins to a build? The idea
>> is to make it easy to construct SDK bundles which contain source,
>> examples, etc.
>>
>> There may be a simple way to do this that I have missed...
>>
>> cheers
>> --oh
>
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03663 seconds
] 
Search
Help
Register
Login
Home
