Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The 'capsule.xyz' properties aren't being read when listed in System-Properties Manifest entry #99

Closed
chrisdchristo opened this issue Feb 4, 2016 · 1 comment

Comments

@chrisdchristo
Copy link
Contributor

So the various system properties, such as capsule.log or capsule.dir are not being read by Capsule on setup when they are listed in the System-Properties manifest entry.

So for example if i have System-Properties: capsule.log=verbose in the manifest entry and then I execute capsule, the logging will not change.

However if I execute Capsule and pass in -Dcapsule.log=verbose, then that works.

Is it intentional to not read the properties from the manifest?

@pron
Copy link
Contributor

pron commented Feb 4, 2016

Is it intentional to not read the properties from the manifest?

Yes! Our intention with capsule is to clearly separate (as much as possible) options that are the application's responsibility from those that are the user's (or deployer's) responsibility. Other deployment products (like Docker) have the same approach. The app says in the manifest: this is what I need to run. The user then says -- on the command line -- this is how I want you to run. On occasion, and for convenience, we allow certain deployment-concern defaults to be specified in the manifest. For example, the default logging level can be set with the Capsule-Log-Level attribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants