Cloning the repository

If you are getting an error while cloning the repository, try running: git config --global http.postBuffer 5000000

This will increase the size of the buffer from the default 1MiB to 5MiB.

To revert this value to the default, use: git config --global http.postBuffer 1000000

The Courses

"Learn Spring" Course:
>> LEARN SPRING - THE MASTER CLASS

"REST With Spring" Course:
>> THE REST WITH SPRING - MASTER CLASS

"Learn Spring Security" Course:
>> LEARN SPRING SECURITY - MASTER CLASS

Java and Spring Tutorials

This project is a collection of small and focused tutorials - each covering a single and well defined area of development in the Java ecosystem. A strong focus of these is, of course, the Spring Framework - Spring, Spring Boot and Spring Security. In addition to Spring, the modules here cover a number of aspects of Java.

Profile based segregation

We are using maven build profiles to segregate the huge list of individual projects we have in our repository.

The projects are broadly divided into 3 lists: default, default-jdk8 and default-heavy.

Next, they are segregated further on the basis of the tests that we want to execute.

Additionally, there are 2 profiles dedicated for JDK17 and above builds - which require JDK 17.

We also have a parents profile to build only parent modules.

Therefore, we have a total of 7 profiles:

Profile	Includes	Type of test enabled
default	JDK17 and above projects	*UnitTest
integration	JDK17 and above projects	*IntegrationTest
default-heavy	Heavy/long running projects	*UnitTest
integration-heavy	Heavy/long running projects	*IntegrationTest
default-jd8	JDK8 projects	*UnitTest
integration-jdk8	JDK8 projects	*IntegrationTest
parents	Set of parent modules	None

Building the project

Though it should not be needed often to build the entire repository at once because we are usually concerned with a specific module.

But if we want to, we can invoke the below command from the root of the repository if we want to build the entire repository with only Unit Tests enabled:

mvn clean install -Pdefault,default-heavy

or if we want to build the entire repository with Integration Tests enabled, we can do:

mvn clean install -Pintegration,integration-heavy

Analogously, for the JDK8 projects the commands are:

mvn clean install -Pdefault-jdk8

and

mvn clean install -Pintegration-jdk8

Building a single module

To build a specific module, run the command: mvn clean install in the module directory.

It can happen that your module is part of a parent module e.g. parent-boot-1,parent-spring-5 etc, then you will need to build the parent module first so that you can build your module. We have created a parents profile that you can use to build just the parent modules, just run the profile as: mvn clean install -Pparents

Building modules from the root of the repository

To build specific modules from the root of the repository, run the command: mvn clean install --pl akka-modules,algorithms-modules -Pdefault in the root directory.

Here akka-modules and algorithms-modules are the modules that we want to build and default is the maven profile in which these modules are present.

Running a Spring Boot module

To run a Spring Boot module, run the command: mvn spring-boot:run in the module directory.

Working with the IDE

This repo contains a large number of modules. When you're working with an individual module, there's no need to import all of them (or build all of them) - you can simply import that particular module in either Eclipse or IntelliJ.

Running Tests

The command mvn clean install from within a module will run the unit tests in that module. For Spring modules this will also run the SpringContextTest if present.

To run the integration tests, use the command:

mvn clean install -Pintegration or

mvn clean install -Pintegration-heavy or

mvn clean install -Pintegration-jdk8

depending on the list where our module exists

License

vikasrathee-cs/tutorials

ErrorLooks like something went wrong!

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages