|
|
| Re: Custom config.ini [message #533657 is a reply to message #533473] |
Sat, 15 May 2010 00:51   |
 Ken
Messages: 36
Registered: July 2009 |
Member |
|
|
Thanks Johannes. The "use an existing config.ini file" is what I was trying,
but it seems like buckminster generates it's own anyway and ignores that
setting. Anyway, your information about adding root files is really what I
was after anyway and that worked out great with both Eclispe export and
running through Buckminster. Thanks!!!
- Ken
"Johannes Utzig" <mail@jutzig.de> wrote in message
news:hsiuta$ouf$1@build.eclipse.org...
> Hi Ken,
>
> please see comments inline.
>
> Am 14.05.2010 04:36, schrieb Ken Prole:
>> I'm using Buckminster with Hudson as per this superb article:
>> http://www.ralfebert.de/blog/eclipsercp/rcp_builds/
>>
>> I'd like to be able to add my own custom properties to the config.ini
>> file that is generated. I got this to work fine using Eclipse product
>> export, but Buckminster does not include it.
>>
>
> In the configuration section of your product definition you can select
> between 'generate a default config.ini file' or 'use an existing
> config.ini file'.
>
>> Does anyone have a solution? If not, is there a way for me to simply add
>> my own text properties file to the root of the exported product. I just
>> want a config file that my application can reference, but do not want it
>> hidden inside my plugin jar, since that would be difficult for an
>> end-user to tweak.
>>
>
> You can add any kind of root file to your product:
> http://help.eclipse.org/galileo/topic/org.eclipse.pde.doc.us er/tasks/pde_rootfiles.htm
>
> Regards,
> Johannes
>
|
|
|
| Re: Custom config.ini [message #533662 is a reply to message #533657] |
Sat, 15 May 2010 02:15 |
Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Can you log an issue for that?
It seems reasonable that Buckminster should understand and honor a
setting that PDE has for "use existing config.ini" (I guess that means
it adds it to the set of root files).
Regards
- henrik
On 5/15/10 2:51 AM, Ken Prole wrote:
> Thanks Johannes. The "use an existing config.ini file" is what I was
> trying, but it seems like buckminster generates it's own anyway and
> ignores that setting. Anyway, your information about adding root files
> is really what I was after anyway and that worked out great with both
> Eclispe export and running through Buckminster. Thanks!!!
>
> - Ken
>
> "Johannes Utzig" <mail@jutzig.de> wrote in message
> news:hsiuta$ouf$1@build.eclipse.org...
>> Hi Ken,
>>
>> please see comments inline.
>>
>> Am 14.05.2010 04:36, schrieb Ken Prole:
>>> I'm using Buckminster with Hudson as per this superb article:
>>> http://www.ralfebert.de/blog/eclipsercp/rcp_builds/
>>>
>>> I'd like to be able to add my own custom properties to the config.ini
>>> file that is generated. I got this to work fine using Eclipse product
>>> export, but Buckminster does not include it.
>>>
>>
>> In the configuration section of your product definition you can select
>> between 'generate a default config.ini file' or 'use an existing
>> config.ini file'.
>>
>>> Does anyone have a solution? If not, is there a way for me to simply add
>>> my own text properties file to the root of the exported product. I just
>>> want a config file that my application can reference, but do not want it
>>> hidden inside my plugin jar, since that would be difficult for an
>>> end-user to tweak.
>>>
>>
>> You can add any kind of root file to your product:
>> http://help.eclipse.org/galileo/topic/org.eclipse.pde.doc.us er/tasks/pde_rootfiles.htm
>>
>>
>> Regards,
>> Johannes
>>
>
|
|
|
Powered by
FUDForum. Page generated in 0.09028 seconds
] 
Search
Help
Register
Login
Home
