| Deployment of own plugins to SMILA [message #565257] |
Tue, 14 September 2010 01:57  |
Eclipse User |
|
|
|
Hello,
we have several plugins that we want to deploy with SMILA. All works fine except for generating the config.ini file in the configuration folder. In the config file there is specify in which start level the plugins to be start. This is necessary for our plugins.
We adapt the SMILA product plugin to add our plugins to the config file while deployment. But this doesn't work :(.
How can we add our plugins to the config file automatically?
|
|
|
| Re: Deployment of own plugins to SMILA [message #565285 is a reply to message #565257] |
Tue, 14 September 2010 03:49  |
| Eclipse User |
|
|
|
Originally posted by: juergen.schumacher.attensity.com
Hi
Am 14.09.2010, 07:57 Uhr, schrieb SMILANewBee <nils.thieme@unister.de>:
> Hello,
>
> we have several plugins that we want to deploy with SMILA. All works
> fine except for generating the config.ini file in the configuration
> folder. In the config file there is specify in which start level the
> plugins to be start. This is necessary for our plugins.
> We adapt the SMILA product plugin to add our plugins to the config file
> while deployment. But this doesn't work :(.
> How can we add our plugins to the config file automatically?
Sorry, I don't know this myself. The config.ini in the SMILA distribution
is currently not generated by the product, but copied from
SMILA.application/configuration, where it is maintained manually.
Maybe this also overwrites your generated config.ini?
However, I agree that it makes sense that this file is generated by the
build.
If you find a soluton and can provide instructions how to set up the
product build
to generate the correct config.ini immediately, I can probably apply the
changes to
the SMILA trunk. But I don't have much time currently for experimenting
with the build. (;
Thanks and Regards,
Juergen.
|
|
|
Powered by
FUDForum. Page generated in 0.05729 seconds
Home