Sorry, I missed this thread the first time round. David is right, the eba-maven-plugin is the best place to start. It does also handle versions using the shared maven2osgiconverter (also used by the bundle plugin).
I'll have a go at an esa-maven-plugin over the next few days. Regards, Graham. On 2 July 2012 13:38, Felix Meschberger <[email protected]> wrote: > Hi, > > Am 02.07.2012 um 12:22 schrieb David Bosschaert: > >> Hi Felix, >> >> On 2 July 2012 11:13, Felix Meschberger <[email protected]> wrote: >>> Am 01.07.2012 um 22:06 schrieb David Bosschaert: >>>> 2. The Subsystem-Content lists all the dependencies of the project. >>>> However, because some of the bundles for this subsystem weren't >>>> developed with OSGi in mind, the start ordering is significant. I >>>> don't know of an easy way to generate this so currently it's hardcoded >>>> and hence duplicated. Also note that fragments obviously don't have a >>>> start-order. >>> >>> Just wondering: How could start order be forced in OSGi ? >>> >>> IIRC there is no such thing as start ordering because such an order can >>> never be guaranteed -- start levels only help to a certain degree. >> >> The start-order is an attribute defined in the Subsystems spec section >> 134.12.1. It simply defines the order in which the bundles are started >> within that subsystem. > > I see, thanks. > > Regards > Felix
