* BAEL-1783
* tabs to spaces, artifact id renamed
* tabs to spaces
* Added module spring-boot-logging-log4j2
* Removed <name> node
* @GetMapping instead of the older @RequestMapping
* @GetMapping instead of the older @RequestMapping
* Moved Lambda examples to separate module
Implementation of API Gateway example
* Format fixes
* Format fixes
* Minor fixes
* Minor fixes
* Minor fixes
* BAEL-1562 - Thymeleaf sample working
* BAEL-1562 Code added for Fragments sample
* BAEL-1562 - Last correction for the test
* BAEL-1562 - Thymeleaf sample working
* BAEL-1562 Code added for Fragments sample
* BAEL-1562 - Last correction for the test
* Updates Thymeleaf version to 3.0.9.RELEASE
* Added msf4j projects
* updated msf4j project folder
* fixed issue with spring-thymeleaf/pom.xml
* Removed depedency-reduced-pom.xml
* Whitespacing fix
* Added parent module on poms that have no parent defined
* Removed dependency reduced pom from undertow module
* Added README
* [BAEL-6729] - Spring modules needs a spring parent
* [BAEL-6729] - Spring modules needs a spring parent
* Added parent module on poms that have no parent defined
* Removed dependency reduced pom from undertow module
* Added README
* [BAEL-6556] - Renamed next set of testcases
* [BAEL-6556] - Renamed next set of testcases
* [BAEL-6556] - Renamed next set of testcases
This commit features a number of tests for programmatically configuring log4j.
Note that in order to have these tests live together, there is a slight deviation in how
these are configured vs how they are in the real world, specifically around static initialization.
Generally speaking, whenever static initialization is needed for a given configuration,
it is embedded in a @BeforeClass-annotated JUnit method.
Also, to isolate the tests from each other's plugins, annotation processing was turned off
in the build. This is not required when doing programmatic configuration of log4j. It is simply
needed for the specific use case of demonstrating these various log4j plugins all in the
same module.
* Added parent module on poms that have no parent defined
* Removed dependency reduced pom from undertow module
* Added new parent pom
* initial clean up of child poms
* Added new parent pom
* [BAEL-5247] - New Parents in the tutorials repo
* Added parent module on poms that have no parent defined
* Removed dependency reduced pom from undertow module
* [BAEL-6056] - Move collection-related logic from core-java to core-java-collections
* [BAEL-6056] - Move collection-related logic from core-java to core-java-collections
* [BAEL-6056] - Move collection-related logic from core-java to core-java-collections
* [BAEL-6056] - Move collection-related logic from core-java to core-java-collections
* Added parent module on poms that have no parent defined
* Removed dependency reduced pom from undertow module
* [BAEL-5249] - 21.02 - pom cleanup - formatted pom.xml
* Added parent module on poms that have no parent defined
* Removed dependency reduced pom from undertow module
* Defined the integration profile in the parent
* add article files
* update kotlin version in pom
* IntelliJ added binary folder to all the .gitignores
* IntelliJ added binary folder to all the .gitignores
* update test function names
* Expand tests and add more code for more meaningful content within the article.
Remove core-kotlin from parent pom again for eclipse to work.
* adjust for issues with custom-pmd
* rename test
* Revert "IntelliJ added binary folder to all the .gitignores"
This reverts commit 0850a2acd5162499540231146c795cfda9ffcfc5.
* Revert "IntelliJ added binary folder to all the .gitignores"
This reverts commit 2b17cf2ff3624ecbe37f07bb9985ecfd3a977e01.
* Adjust config
* Adjust config
* Adjust config
* fix
* fix
* Rename MetricTypeTest
* Rename MetricTypeTest
* Rename MetricTypeTest
* Rename MetricTypeTest
* Install custom pmd jar to local maven repo during maven validate phase, so that it becomes available during project build
* maven install plugin - adding base path
* changed the phase for maven directory plugin to validate to make sure that the base directory variable is available to maven install plugin
* pmd violation flag back to false
* Failing build if unit test name does not follow one of the following conventions : ..IntegrationTest, ..LongRunningUnitTest, ..ManualTest, ..JdbcTest, ..LiveTest
* Custom PMD Rules project
* Fixed this issue when unit test classes were not being scanned by custom PMD rule (This happened after I pulled code from upstream project)
* Don't fail the build if PMD custom rule fails
* Reconfigure PMD
* Reformat POM
* Adjust PMD rules
* Rename test
abialas
Andrea Ligios
Mariusz Kuligowski
eelhazati
Loredana Crusoveanu
markusgulden
Sanjay Patel
Bahtiyar Kaba
Loredana Crusoveanu
psevestre
Pello Altadill
Eugen Paraschiv
Grzegorz Piwowarek
Amit Pandey
eelhazati
BQ
Loredana Crusoveanu
Josh Cummings
Dhrubajyoti Bhattacharjee
Timoteo Ponce
Tom Hombergs
Karan Khanna
Wosin
ShyamVeda
pauljervis
mherbaghinyan