On Mon, Dec 16, 2013 at 12:27 AM, Carsten Ziegeler <[email protected]> wrote:
> Hi,
>
> actually I think this should work :) Are those bundles in question
> installed by the Sling installer or by launchpad?
Not sure which one kicks in when, so I'll just say that in my list.xml
I have something like
<startLevel level="15">
<!-- other stuff -->
<bundle>
<groupId>org.liquibase</groupId>
<artifactId>liquibase-osgi</artifactId>
<version>3.0.1</version>
</bundle>
</startLevel>
The bundle's location is shown as 'slinginstall:liquibase-osgi-3.0.1.jar'.
> Can you see that the new launchpad jar gets extracted when you start it -
> does it overwrite the old one?
Where in the 'sling' folder should I look?
Thanks,
Robert
>
> Carsten
>
>
> 2013/12/16 Robert Munteanu <[email protected]>
>
>> Hi,
>>
>> I'm trying to find out what is the proper way of delivering an updated
>> bundle list to a launchpad-based application.
>>
>> I took the following steps:
>>
>> 1. Built a launchpad using a basic bundle list and executed the jar
>> with java -jar
>> 2a. Added a new bundle to list.xml and rebuilt the jar . Executed the
>> jar with the same sling directory
>> 2b. Increased a bundle's version in list.xml and rebuilt the jar .
>> Executed the jar with the same sling directory
>>
>> Both 1+2a and 1+2b left me with the same bundle list from 1. Just to
>> be on the safe side, I additionally updated the launchpad's version,
>> but that still did not work.
>>
>> I know about using the Felix console and the maven-sling-plugin, but
>> sometimes it's easier to deliver one updated launchpad jar. This leads
>> me to wonder, how can I update the bundles which are delivered with a
>> launchpad?
>>
>> Thanks,
>>
>> Robert
>>
>
>
>
> --
> Carsten Ziegeler
> [email protected]
--
Sent from my (old) computer
