| Summary: | [tooling] provide log level for jetty | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Benjamin Muskalla <b.muskalla> | ||||
| Component: | Tools | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | ||||||
| Version: | 1.3 | ||||||
| Target Milestone: | 1.3 M2 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Benjamin Muskalla
I wonder whether users really need that level of configuration for RAP development? We could also add controls to enable HTTPS in jetty (which needs at least 3 controls...) and I guess there are more ideas. I think we should focus on RAP-related configuration in the launcher. If we add a parameter to set the log level to "info" by default - wouldn't that make almost everyone happy? As long as an advanced user can still override the flag by specifying a VM argument I'm fine with just adding it in the background :) Created attachment 143851 [details]
patch+testcase
Patch to add the log level "info" as default.
I wonder why we prefer values set by the launcer over custom values. Changed the order (see failing test).
In my eyes we should allow to override the values set by the launer (and changing the testcase accordingly)
We agreed to not switch the order but adding the default log level to new RAP launch configs. This we users are still able to override it without touching the launcher too much. Fixed in CVS HEAD |