https://github.com/dlsc-software-consulting-gmbh/dlsc-maven-parent

Parent POM for all Maven based DLSC projects.
https://github.com/dlsc-software-consulting-gmbh/dlsc-maven-parent

Last synced: 28 days ago
JSON representation

Parent POM for all Maven based DLSC projects.

• Host: GitHub
• URL: https://github.com/dlsc-software-consulting-gmbh/dlsc-maven-parent
• Owner: dlsc-software-consulting-gmbh
• License: apache-2.0
• Created: 2021-11-07T17:09:43.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2024-06-03T09:57:12.000Z (11 months ago)
• Last Synced: 2025-01-30T05:12:35.491Z (3 months ago)
• Size: 84 KB
• Stars: 0
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.adoc
  • License: LICENSE

Awesome Lists containing this project

README

        
= dlsc-maven-parent

:project-owner:      dlsc-software-consulting-gmbh

:project-name:       dlsc-maven-parent

:project-groupId:    com.dlsc

:project-artifactId: dlsc-maven-parent

:project-version: 1.5.0

image:https://github.com/{project-owner}/{project-name}/workflows/Build/badge.svg["Build Status", link="https://github.com/{project-owner}/{project-name}/actions"]

image:https://img.shields.io/maven-central/v/{project-groupId}/{project-artifactId}.svg[Download, link="https://search.maven.org/#search|ga|1|g:{project-groupId} AND a:{project-artifactId}"]

---

Parent POM for all DLSC projects.

== Profiles

The parent POM enables the following profiles:

* `publication`: generates sources and javadoc JARs.

* `gpg`: signs all attached artifacts.

* `local-deploy`: deploys all artifacts to a target directory defined by `${local.repository.path}`

== Requirements

Children projects must define values for the following properties

Given a project named `foo` located at `dlsc/foo`:

[source,xml]

[subs="verbatim"]

----

    foo

    dlsc/foo

    /tmp/repository

    dlsc-software-consulting-gmbh_Foo

    1.8

    1.8

    1.8

----

== Constraints

The `` block must be defined explicitly at the root of the child project, otherwise the URLs will be set to the wrong

paths. Given a project named `foo` located at `dlsc/foo`:

[source,xml]

[subs="verbatim"]

----

    scm:git:${repository.url}

    scm:git:${repository.url}

    ${repository.url}

    HEAD

----

The `license-maven-plugin` must be defined at the root of the child in order to find the license header template at the

right location

[source,xml]

[subs="verbatim"]

----

    com.mycila

    license-maven-plugin

    

        ${rootdir}/etc/license.txt

        true

        

            README.md

            LICENSE

            mvnw

            mvnw.cmd

            .mvn/wrapper/*

            ...

        

    

----