gCubeSystem
/
maven-parent
15
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
conflict
bug/25877
bug/25872
bug/26841
feature/25414
feature/25106
feature/24259
feature/24580
feature/23905
feature/23897
feature/23893
feature/22914
feature/22842
20116
fix/19939
fix/19854
fix-filtered-gcube-resource
feature/19662
resolve-eclipse-requirements
maven-enforcer-plugin-version
unified-version-plugins
18994
feature/18534
feature/17809
feature/17603
feature/17358
feature/16915
no-openjdk
feature/16914
feature/16710
feature/16697
v1.2.0
v1.1.0
r5.8.1
r5.7.0
r5.6.1
r5.6.0
r5.5.0
r5.4.2
r5.4.1
r5.4.0
r5.3.1
r5.3.0
r5.2.0
r5.16.1
r5.15.3
r5.15.0
r5.1.0
r5.0.1
r5.0.0
r4.28.0
r4.27.0
r4.26.0
r4.25.1
r4.24.0
r4.23.0
r4.22.0
r4.21.0
r4.20.0
r4.19.0
r4.15.0
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
maven-parent/README.md

2.4 KiB
Raw Permalink Blame History

MAVEN PARENT POM

A parent pom for all the gCube artifacts.

Enforcements

  • Java 8 (target and source) unless otherwise specified inside the pom
  • OpenJDK as target Java VM.
  • Maven 3.3.9+
  • README.md, CHANGELOG.md and LICENSE.md are present in the baseDir of each Maven module
  • CHANGELOG.md must declare a tag [v+Pom version] (e.g. [v1.0.0])

Build Profiles

The build profiles are separated in three main branches: developer, staging, releases. Each branch has a set of profile based on the idk. The developer branch contains the profiles related to the snapshot build:

  • gcore-legacy jdk7
  • gcube-legacy - jdk8
  • gcube-official -jdk11
  • gcube-experimental - jdk17

In the same way are organised the other branch profiles related to the staging (integration) phase and to the release phase.

In addition there are a set of common profiles useful in order to avoid replication of plugins and rules definitions:

  • common-snapshot
  • common-release
  • dry-run
  • disable-java8-doclint
  • set-local-classpath
  • generate-distribution-packages

Below the descriptions of the most used profiles by gCube components:

common-snapshot

This profile defines the common plugin used by all the snapshot profiles

common-releases

This profile defines the common plugin used by all the staging and release profiles

gcube-official

  • Dependencies resolved against local, gcube-snapshots and gcube-releases
  • Snapshot artifacts installed to local
  • Snapshot artifacts deployed to gcube-snapshots
  • Deployments of releases artifacts are not permitted

jenkins-staging-official

  • Dependencies resolved against local-staging, gcube-jenkins-staging, gcube-staging and gcube-releases
  • Release/snapshot artifacts installed to local-staging
  • Release/snapshot artifacts deployed to gcube-jenkins-staging

jenkins-releases

  • Dependencies resolved against local-releases, gcube-releases, gcube-jenkins-staging and gcube staging
  • Release artifacts installed to local-releases
  • Deployments of snapshot artifacts are not permitted
  • Release artifacts deployed to gcube-releases

dry-run

This profile disables the deployment of the artifacts.

disable-java8-doclint

This profile sets an additional parameter for javadoc generation to disables the doclint. It avoids the build fails if formal/syntax errors are found in javadoc comments.

set-local-classpath

This profile set a generic folder that will be added to the classpath