commit | cbbd42e750aca7468fa395a416bc9effc39dadae | [log] [tgz] |
---|---|---|
author | Beat Schwarzentrub <bsh@bsiag.com> | Mon Feb 20 09:07:51 2017 +0100 |
committer | Beat Schwarzentrub <bsh@bsiag.com> | Mon Feb 20 19:09:52 2017 +0100 |
tree | 1203a2398be22e384eecdbf97f89033f729c7940 | |
parent | d4e1110acb9f8bbcba080fca971676bd44bd3f30 [diff] |
Platform: Include invalid property names in exception message In some runtime environments (i.e. during CI tests), the logger might not be available when the config.properties file is validated. The names of the invalid properties would then be unknown which makes the error hard to fix. Including the invalid property names in the exception message can help in this case. [CP from 6.1.x] Change-Id: I0e1c3b14264f3aa7e73ff8e98c13e2fcce076ab5
[Eclipse Scout] 1 is a mature and open framework for modern, service oriented business applications. It substantially boosts developer productivity and is simple to learn.
This Repository Eclipse Scout RT contains the source for the runtime components embedded in the applications build on top of the Eclipse Scout Framework.
The content of this repository is build on the Eclipse infrastructure and the different versions are available on several [P2 Update Sites] 2.
The easiest way to start with Eclipse Scout is to download Eclipse for Scout Developers Eclipse for Scout Developers on the [Eclipse downloads page] 3.
We welcome any kind of contributions (Bug report, documentation, code contribution...). Please read the [Eclipse Scout Contribution page] 7 to know more about it.
The contribution process of Eclipse Scout is hosted on tools deployed by the Eclipse Foundation (involing [Bugzilla] 6, Gerrit, Hudson, MediaWiki...).
External tools like the GitHub tracker and pull requests are not supported.
To get in touch with the Eclipse Scout community, please open a thread in the [Eclipse Scout Forum] 5 or send a mail to [our mailing list] 8: scout-dev@eclipse.org
[Eclipse Public License (EPL) v1.0] 9