I noticed in a project that any startlevel set using the -runbundles+ decorator does not show-up in the -runbundles outputted by the bnd-resolver-maven-plugin. Note that if the bndrun also includes a -runstartlevel instruction, then the output of bnd-resolver-maven-plugin will include startlevel attribute, but only with the value(s) following from the -runstartlevel instruction, and not from the -runbundles+ decoration.
When a bndrun file that uses a -runstartlevel instruction and some specific startlevels assigned using -runbundles+ decoration is generated into an executable JAR, then the resulting startlevels used within that executable JAR is the expected combination of both.
Is it to be expected that the output of the bnd-resolver-maven-plugin with respect to startlevel attributes is aligned with the effective output of the bnd-exporter-maven-plugin?
pkriens
commented
6 days ago
I noticed in a project that any startlevel set using the
-runbundles+decorator does not show-up in the-runbundlesoutputted by thebnd-resolver-maven-plugin. Note that if the bndrun also includes a-runstartlevelinstruction, then the output of bnd-resolver-maven-plugin will include startlevel attribute, but only with the value(s) following from the-runstartlevelinstruction, and not from the-runbundles+decoration.When a bndrun file that uses a
-runstartlevelinstruction and some specific startlevels assigned using-runbundles+decoration is generated into an executable JAR, then the resulting startlevels used within that executable JAR is the expected combination of both.Is it to be expected that the output of the
bnd-resolver-maven-pluginwith respect to startlevel attributes is aligned with the effective output of thebnd-exporter-maven-plugin?