Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions content/tools-in-intellij/reading/debugging/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ originalAuthor: Sally Steuterman # to be set by page creator
originalAuthorGitHub: gildedgardenia # to be set by page creator
reviewer: # to be set by the page reviewer
reviewerGitHub: # to be set by the page reviewer
lastEditor: # update any time edits are made after review
lastEditorGitHub: # update any time edits are made after review
lastMod: # UPDATE ANY TIME CHANGES ARE MADE
lastEditor: Terri Penn # update any time edits are made after review
lastEditorGitHub: tpenn # update any time edits are made after review
lastMod: 2023-09-24T09:55:31-05:00 # UPDATE ANY TIME CHANGES ARE MADE
---

{{< youtube 1bCgzjatcr4 >}}
Expand Down Expand Up @@ -38,15 +38,15 @@ You should have already downloaded this code from `java-web-dev-projects`.
1. Run your program in **Debug mode**.
1. Inspect the values of your variables in the **Debugger Pane**.
1. If needed, use the **Add/Watch** button to watch a specific expression as your program executes.
1. You can also set a **conditional breakpoint** to pause the execution of the code when a certain condition is a method.
1. You can also set a **conditional breakpoint** to pause the execution of the code when a certain condition is met.

## Control the Flow of Execution

1. **Step-over** button executes a given line then steps to the next executable line
1. **Step-into** button allows you to review a called method and see what is going to line within the method
1. **Step-into** button allows you to review a called method and step line by line within the method
1. **Step-out-of** button allows you to move out of the method you stepped into and resume stepping through the main code
1. **Variables Pane** allows you to examine how variables are manipulated within your code. Also allows you to identify specific *Watch expressions*
1. **Frames Pane** tracks any method calls and threads in your code line by line. Best used with breakpoints.
1. **Variables Pane** allows you to examine the current values of variables and how they are manipulated within your code. Also allows you to identify specific *Watch expressions*
1. **Frames Pane** tracks any method calls and threads in your code. This provides a stack trace view, showing the call hierarchy of methods and threads currently in execution. Best used with breakpoints.

## Advantage of Debugger Over Printing to the Console

Expand Down
13 changes: 6 additions & 7 deletions content/tools-in-intellij/reading/gradle/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ originalAuthor: Sally Steuterman # to be set by page creator
originalAuthorGitHub: gildedgardenia # to be set by page creator
reviewer: # to be set by the page reviewer
reviewerGitHub: # to be set by the page reviewer
lastEditor: # update any time edits are made after review
lastEditorGitHub: # update any time edits are made after review
lastMod: # UPDATE ANY TIME CHANGES ARE MADE
lastEditor: Terri Penn # update any time edits are made after review
lastEditorGitHub: tpenn # update any time edits are made after review
lastMod: 2023-09-24T09:41:55-05:00 # UPDATE ANY TIME CHANGES ARE MADE
---

By now you have created at least two Spring projects using Gradle. If you recall, Spring is the framework that will enable us to create an MVC application. When we created each project, we selected "Gradle Project", but what is Gradle?
Expand All @@ -32,7 +32,7 @@ So far we have included Gradle in our Spring Boot projects.

## How Gradle Works

A Gradle build represents one or more **projects**. Projects are craeted from a series of **tasks**. Gradle manages tasks based on their function in the build. Some tasks run tests, some compile, etc. Gradle organizes these tasks in the `build.gradle` file.
A Gradle build represents one or more **projects**. Projects are created from a series of **tasks**. Gradle manages tasks based on their function in the build. Some tasks run tests, some compile, etc. Gradle organizes these tasks in the `build.gradle` file.

### `build.gradle`

Expand Down Expand Up @@ -83,8 +83,7 @@ Some projects contain a stand-alone `configurations` method. This method bundles

{{% notice blue "Note" "rocket" %}}

In the `hello-spring` project, the `build.gradle` file contains a configurations method.
The `hello-spring` project does not.
None of the `build.gradle` files in projects up to this point contained a configurations method. The upcoming studio `Spa Day!` will.

{{% /notice %}}

Expand All @@ -107,7 +106,7 @@ IntelliJ’s built-in IntelliSense should prompt you to refresh your build.gradl
you change a file. You should see a small icon appear in the top right corner of the `build.gradle` file.
If you click on the icon, it will refresh your build.
If you update `build.gradle` and the icon does not appear, you can manually refresh the build.
**Mac Users** try *Up + Command + I* and **Windows/Linux Users** try *Control + Shift + O*.
**Mac Users** try *Shift + Command + I* and **Windows/Linux Users** try *Control + Shift + O*.

For more on Gradle and IntelliJ, visit this [website](https://www.jetbrains.com/idea/guide/tutorials/working-with-gradle/gradle-dependencies/).

Expand Down