When configuring startlevels in profile documents, the syntax for osginsf bundles is quite clumsy.
As far as I found out, I have to use a full path like
osginsf:javaddin/updatesite.nsf/76B4F9E169F759F9C125790C0048064F/org.eclipse.equinox.ds_1.2.1.r36x_v20100803.jar
The path contains the UNID of the Notes document hosting the bundle as well as any timestamps in the version, so every time I import an update site into the update site database, I have to figure out the paths of all bundles that require startup configuration again.
My requests in this context are:
- Is there a shorter syntax for addressing osginsf bundles that I missed? If not, is there any chance to create such a feature?
- It would also be helpful to have a wider input field for the startlevel configuration in the profile document.
Regards,
Harald