Set up VS Code for debugging Java and Frontend#825
Conversation
|
@stuartrowe, @timja, @lewisbirks, what do you think? |
timja
left a comment
There was a problem hiding this comment.
Looks fine (untested), definitely don't want maven to re-run on changes. It will live reload anyway for frontend changes like jelly, and some Java changes are hotswappable (compile again without restarting), like changing method bodies
By the way, there must be something wrong in this plugin's Jenkins setup. When pressing |
lewisbirks
left a comment
There was a problem hiding this comment.
Looks good to me, I don't use VS Code but they look right, one minor thing but I'm happy regardless
Yeah, I've never seen that work in this plugin (no experience with others to compare it to) |
I've never seen it work in any plugin, you don't really want it running in an interactive terminal as its easy for that to happen, I run it intellij where it doesn't trigger. |
|
I'll play around with IntelliJ and see if I can create similar configurations for running (in a separate PR) |
| ``` | ||
|
|
||
| - Ensure Maven >= 3.9.9 is installed and included in the PATH environment variable. | ||
| - Ensure Maven >= 3.9.9 is installed and included in the `PATH` environment variable. |
There was a problem hiding this comment.
should we include a maven wrapper 🤔
not one for this PR probably but something to think about @timja
There was a problem hiding this comment.
I have no strong opinion about it.
|
Alright, I have no further changes for this PR. It can be merged whenever you guys feel like. |
Closes #813.
Testing done
Debugging.mp4
Submitter checklist
Open questions
nodemonto re-run the Maven process whenever the bundled files change, but Maven takes too long to fully initialize Jenkins, I'm not sure it's worth it.