This is from an email exchange during the review of the JEP.

Mandy's comments start with ">"

> 2. Under "Modular application" section:
>
>    "When creating an application image from a modular application, jpackage will run jlink with a default set of arguments, using the provided module as the root module with all service providers added, to produce the Java runtime image that will be used to run the application. "
>
> "default set of arguments" is not clear what it means.  Does it run `--bind-services` by default?   it'd be help to make it clear for example "jpackage will run jlink with the main module and additional modules specified in `--add-modules` option as the root module with service binding."?

Yes, it does run '--bind-services' by default (as in the non-modular application case). It is a good question as to whether it should do this for modular apps (see below).

> Is service binding the default for packaging modular application?   I wonder if service binding should not be the default and instead the user should specify explicit list of modules via --add-modules.  It may also be useful to add jpackage --bind-services so that it can be supplied when invoking the jpackage command and pass it to jlink.

While we don't want to add too many such options, this one makes sense to reconsider if we decide to not pass it by default for modular apps.

> This can be an open issue to follow up after integration.

OK. We will file a follow-on JBS issue (for 13) to consider what the default for '--bind-services' should be for modular applications and whether we should add a '--bind-services' options to jpackage.