Hi Richard,
I am running a bash script which sends some gogo deployment commands to
install some bundles in felix. I then list the bundles I just deployed
with gogo with the command 'lb'. These bundles are all correctly
displayed and have their state set to active. At the end of the script
Felix then terminates (I assume because it is called non-interactively
via a script).
Now if I startup this exact same deployment and list the installed
bundles via 'lb', all I get is the bundles I previously copied into the
bunde/ subdirectory. The bundles I installed via gogo have disappeared,
although I never undeployed them.
What am I missing?
Here is a minimal version of my deployment script:
#!/bin/bash
java -verbose -jar bin/felix.jar <<-END_GOGO_SCRIPT_STARTUP
obr:repos add file:$HOME/.m2/repository/repository.xml
obr:deploy -s "Some bundle from maven repo"
felix:refresh
felix:lb
END_GOGO_SCRIPT_STARTUP
Best regards,
Sam
Am 19.10.11 17:23, schrieb Richard S. Hall:
> On 10/19/11 03:24 , Sam Spycher wrote:
>> Hi
>>
>> I am currently writing a small shell script which is supposed to run
>> felix, install the necessary bundles with gogo, then quit and package
>> felix for deployment on our integration servers.
>>
>> Unfortunately, felix seems to undeploy the deployed bundles when
>> shutting down. If I do this manually, felix retains the bundles across
>> shutdowns and startups.
>
> I'm not sure what you mean, nor what you are doing exactly, but the
> Felix framework always retains bundles across shutdowns and restarts.
> The framework will never undeploy a bundle unless someone tells it to do
> so.
>
> -> richard
>
>>
>> The only difference I can find is on how I exit Felix. From the script,
>> felix exits "normally", and when configuring interactively I exit with
>> Ctrl-C.
>>
>> -> so my question is: how can I persuade Felix to keep the installed
>> bundles (and keep their active state) across shutdowns and startups?
>>
>> -> would the proper way to do this be over config.properties?
>>
>> -> if yes, and if this means that deployment of bundles happens on every
>> startup, then how do I work around the issue of potentially not having
>> access to a repo on the server that felix is to be installed?
>>
>>
>> Here is the part of the script which uses gogo:
>>
>> #!/bin/bash
>> # ...
>> # GOGO deployment script
>> cat> $GOGO_SCRIPT<<-END_GOGO_SCRIPT
>> obr:repos add file:$HOME/.m2/repository/repository.xml
>> obr:deploy -s "Bundle A"
>> obr:deploy -s "Bundle B"
>> obr:deploy -s "Bundle C"
>> # etc.
>> felix:refresh
>> felix:lb
>> END_GOGO_SCRIPT
>> # ...
>> # run felix and GOGO script
>> java -verbose -jar bin/felix.jar -<<-END_GOGO_SCRIPT_STARTUP
>> gosh --nointeractive --login -x $GOGO_SCRIPT
>> END_GOGO_SCRIPT_STARTUP
>>
>>
>> Thanks for any help,
>> Sam
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
>> For additional commands, e-mail: users-h...@felix.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> For additional commands, e-mail: users-h...@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
