Spring Code Challenges

This is the repository for the LinkedIn Learning course Spring Code Challenges. The full course is available from LinkedIn Learning.

Spring is one of the most popular Java frameworks, and if you’re a developer, that means that you not only have to understand Spring, you also have to constantly update your skills and continue learning about Spring. In this course, Cecili Reid presents 10 different Spring-related challenges through a Java application. She tests your knowledge of Spring features like setting up an actuator, scheduling jobs, providing images for client request, bulk importing with Spring Batch, and more. You can complete the challenges in any order, then compare your solutions to Cecili’s. Whether you’re looking to test your existing knowledge or learn something new, this course can give you a good idea of the current state of your Spring skills.

Instructions

This repository has branches for each of the videos in the course. You can use the branch pop up menu in github to switch to a specific branch and take a look at the course at that stage, or you can add /tree/BRANCH_NAME to the URL to go to the branch you want to access.

Branches

The branches are structured to correspond to the videos in the course. The naming convention is CHAPTER#_MOVIE#. As an example, the branch named 02_03 corresponds to the second chapter and the third video in that chapter. Some branches will have a beginning and an end state. These are marked with the letters b for "beginning" and e for "end". The b branch contains the code as it is at the beginning of the movie. The e branch contains the code as it is at the end of the movie. The main branch holds the final state of the code when in the course.

When switching from one exercise files branch to the next after making changes to the files, you may get a message like this:

error: Your local changes to the following files would be overwritten by checkout:        [files]
Please commit your changes or stash them before you switch branches.
Aborting

To resolve this issue:

Add changes to git using this command: git add .
Commit changes using this command: git commit -m "some message"

Instructor

Cecili Reid

Check out my other courses on LinkedIn Learning.