[DOCU-675] Create a tips & tricks page for different dev. environments and coding approaches Created: 17/Feb/16 Updated: 30/Sep/19 Resolved: 30/Sep/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | outdated | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
I must confirm that this is a bit a vague ticket yet E.g. apchelintcev was just creating Classpath resources in development mode which explains how to work with intelliJ when developing and changing files on the classpath. Please also ask zgreant who was starting tips for light developers for nice filtered log & similar things. |
| Comments |
| Comment by Zak Greant [ 18/Feb/16 ] |
|
You can use the grep shell command to filter out parts of your logs – even if you are using tail -f to monitor additions to a particular log file. This is particularly useful when you want to do things like exclude the details from stack traces or just focus on the light development messages. Here's an example showing how to get a live feed from your catalina.out log with most of the details for stack traces removed.
tail -f catalina.out | grep -v --line-buffered --invert-match "^\t\(at\|\.\.\.\) "
# --line-buffered option makes grep work on a line-by-line basis
|
| Comment by Julie Legendre [ 30/Sep/19 ] |
|
In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed. |