You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have added custom start levels in -runstartlevel for few bundles. We have in the meanwhile (~5-6 months ago) removed some bundles from the workspace but the corresponding entries still exist in the -runstartlevel instruction. Now, in 6.3, if I start the bndrun which inherits this -runstartlevel, it reports the problem as enclosed. It seems that -runstartlevel now behaves like -runbundles. If I remove these obsolete entries from -runstartlevel, everything works fine. But, it used to work perfectly in 6.2-REL.
I know that we should remove those obsolete entries from -runstartlevel but still I wanted to let you know if the behaviour of -runstartlevel has now been changed in the meanwhile so that it doesn’t introduce any other lurking issues in future.
The text was updated successfully, but these errors were encountered:
We have added custom start levels in
-runstartlevel
for few bundles. We have in the meanwhile (~5-6 months ago) removed some bundles from the workspace but the corresponding entries still exist in the-runstartlevel
instruction. Now, in 6.3, if I start the bndrun which inherits this-runstartlevel
, it reports the problem as enclosed. It seems that-runstartlevel
now behaves like-runbundles
. If I remove these obsolete entries from-runstartlevel
, everything works fine. But, it used to work perfectly in 6.2-REL.I know that we should remove those obsolete entries from
-runstartlevel
but still I wanted to let you know if the behaviour of-runstartlevel
has now been changed in the meanwhile so that it doesn’t introduce any other lurking issues in future.The text was updated successfully, but these errors were encountered: