fugerit-org/fj-bom

Fugerit Java BOM to use as parent pom

fj-bom's Issues

Fix compatibility wiht maven source plugin 3.3.0

There is a but which prevents this bom to attach properly the sources with the lastest version of maven source plugin

Sonar cloud maven build

Add sonar cloud maven build github action workflow

The workflow will activate for commit on :

• main
• branch-sonarcloud
• pull requests

Quality gate will be shown on the readme :

Sonar keys are passed as maven parameters to avoid child projects have import them

mvn -B verify org.sonarsource.scanner.maven:sonar-maven-plugin:sonar -Pcoverage -Dsonar.host.url=https://sonarcloud.io -Dsonar.organization=fugerit-org -Dsonar.projectKey=fugerit-org_fj-bom

Fix to license url

The license url in the license section of the pom is diffierent from the default property.
Set the project to use the same.

Add fj-bom documentation

The goal is to create markdown documentation for :

• scope of the bom
• profile usage
• dependancy management

Move to keep a changelog style

New changelog style based on :
https://github.com/olivierlacan/keep-a-changelog

Changeg badge shown on README.md

General support for sonar cloud scan

To be able to run sonar cloud scan via maven build on github action, it is required to activate the 'coverage' profile.

The coverage maven profivole activate the test and add the jacoco-maven-plugin for coverage reporting.

Add build metadata to MANIFEST

• Maven profile 'doRelease' should activate buildnumber-maven-plugin and add metadata to MANIFEST.MF

The properties added are :

• 'Bundle-License' (values is the 'licenseURL' maven property)
• 'Bundle-Description' (values is the 'project.description' maven property)
• 'Bundle-Name' (values is the 'project.name' maven property)
• 'Bundle-ManifestVersion' set to 4 (https://docs.osgi.org/download/r8/osgi.core-8.0.0.pdf)
• 'Implementation-Build' (values is the 'buildNumber' from buildnumber-maven-plugin)
• 'addDefaultImplementationEntries' from maven-jar-plugin

Maven deploy github action

Security update : slf4j

Security update for sll4j

Starting with version 1.0.0 : Java 11 should be used for building (maven.compiler.release can still be set to java 8)

To comply with some test time libraries (for instnace hsqldb) library should be built with java11.
It is still possibile to use java 1.8 (8) as compliance level, for instance :

            <java-version-compliance>8</java-version-compliance>
	    <maven.compiler.source>${java-version-compliance}</maven.compiler.source>
	    <maven.compiler.target>${java-version-compliance}</maven.compiler.target>	
	    <maven.compiler.release>${java-version-compliance}</maven.compiler.release>