Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/421
this is classic only, as that's what the docker container uses at present
(and the normal brooklyn dist), and it was easier to get going.
fully accept that when we move to osgi we'll have to change and do this all
another way.
BTW i had been thinking the move to osgi would drop these args, most args
in fact, in favour of config files and sending additional commands to the
server afterwards, and we'd have to rebuild the `Dockerfile` of course.
however it's worth bearing in mind that that the multi-command approach is a
little tedious in docker-land however, as containers prefer the
"just-one-process" model ... and many shells like alpine don't have job control
to be able to background. entirely possible but maybe worth a discussion about
whether to send startup instructions / duplicate this flag to brooklyn osgi or
not.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
