|
Description:
|
Some requirements:
* Validating quickstart POM files:
** Check for the License header (checkstyle headers) - Headers templates must be updated: https://github.com/jboss/ide-config/pull/6
** Check for proper spacing and Indentation (try checkstyle - whitespace rule and indentation rule)
** Check and verify if all quickstarts are using the same/latest BOM versions
** Verify is it using the standard properties names (We will provide the standard properties name)
** Check for non bom versions (and identify if we should create a new BOM)
** Check javascript and css versions
** Check for duplicate properties and dependencies
** Check
for unused properties on project and its modules
** Check
the pom.xml elements order
** Create scripts to update versions (quickstart, boms, etc)
** When a new quickstart is added, if it has a pom.xml file, make sure the <module> is defined in one of the following profiles: default, requires-postgres, complex-dependencies, requires-full, requires-xts, non-maven.
* Validating quickstart README files:
** Check for the required metadata tags in README (Level, Author, Target Product, etc)
** Verify the quickstart name in the README matches the folder name and the project name
* Validating quickstart source code
** Check the quantity of comments in the code (evaluate PMD)
* General validation (desired):
** If a quickstart with a source other than the current repository is modified, create an alert of some sort so we can notify the upstream repository of the change.
** When we update a BOM property version in the quickstarts, we need to make the same changes in the archetypes.
** Also, if there is a code fix in the kitchensink or kitchensink-ear, we need to make the same fix in the archetype code and check other quickstarts based on the same archetype to see if they need the fixes applied.
|
