* Adding support for maven assembly plugin to generate executable jar with all dependencies in built
* Merge branch 'master' into issue-989
# Conflicts:
# abstract-document/pom.xml
# pom.xml
* Adding maven assemly plugin for projects with name A
* Update in format as per checkstyle, i.e. Spcae in place of tab with size of 2
* batch set - 2 having all project with B and C
* issue-989 d-e-f
* fixing eip pom and adding g-h-i-l-m-n Skipping naked object as it seems it doesn't have main method, will consider this at end
* Adding for O and P projects Skipping Object-Mother as we don't have main method for same.
* Add custom license header style in order to comply with Google's Checkstyle format
* Update license headers to comply with Google's Checkstyle format
* #496 Add pipeline module to parent pom ✨
* #496: Add main application class and test for pipeline
* #496: Checkstyle format and add log messages on pipeline stages 🎨
* #496: Fill readme sections of pipeline ✨
* #496: Javadocs and checkstyle formatting 🎨
* #496: Follow PMD checks and add more explanation as block comment on App.java
* #496: Apply requested PR changes by iluwatar 🎨
* #970: Replace log4j usage on commander pattern to Slf4j API 🎨
* #970: Replace log4j usage on dao pattern to Slf4j API 🎨
* #970: Replace log4j usage on data mapper pattern to Slf4j API 🎨
* #970: Remove log4j dependency on data transfer object pom 🔥
* #970: Replace log4j usage on module pattern to Slf4j API 🎨
* #970: Replace log4j usage on serverless pattern to Slf4j API 🎨
This also removes the aws log4j dependency
* #970: Remove unnecessary gitignore line for log4j.xml 🔥
* #970: Remove remaining remnants of log4j 🔥
* #970: Replace System.out logging with appropriate logging methods 🎨
* #970: Replace System.out method references to Logger::info 🎨
* Made minor changes in some patterns such as removed throws clause where not needed, changed incorrect order of arguments in assertEquals
* Minor refactorings and code style changes. 1) Removed several use of raw types 2) Removed unnecessary throws clauses 3) Used lambda expressions wherever applicable 4) Used apt assertion methods for readability 5) Use of try with resources wherever applicable 6) Corrected incorrect order of assertXXX arguments
* Removed unused import from Promise
* Addressed review comments
* Addressed checkstyle issue
resources (Connection, Statement and resultSet) until the stream is
closed by the consumer. So try-with-resources is not an option as per
sonarqube’s recommendation. But it is still recommended to close
statement and result set. When connection pool used, connection is not
closed when close() called. It is just returned to the pool.
Using //NOSONAR to avoid false blocker issue.
