Concord Maven Build Extension

The Concord Maven Plugin provides a packing and lifecycle for Concord plugins

License

License

Categories

Categories

Maven Build Tools
GroupId

GroupId

ca.vanzyl.concord
ArtifactId

ArtifactId

concord-maven-plugin
Last Version

Last Version

0.0.3
Release Date

Release Date

Type

Type

takari-maven-plugin
Description

Description

Concord Maven Build Extension
The Concord Maven Plugin provides a packing and lifecycle for Concord plugins

Download concord-maven-plugin

Dependencies

compile (3)

Group / Artifact Type Version
org.eclipse.aether : aether-api jar 1.1.0
org.codehaus.plexus : plexus-utils jar 3.0.17
org.apache.maven : maven-artifact jar 3.2.3

provided (3)

Group / Artifact Type Version
org.apache.maven : maven-plugin-api jar 3.2.3
org.apache.maven.plugin-tools : maven-plugin-annotations jar 3.2
org.apache.maven : maven-core jar 3.2.3

test (4)

Group / Artifact Type Version
io.takari.maven.plugins : takari-plugin-testing jar 2.9.1
io.takari.maven.plugins : takari-plugin-integration-testing pom 2.9.1
junit : junit jar 4.11
org.assertj : assertj-core jar 3.15.0

Project Modules

There are no modules declared in this project.

Takari POM

The parent POM for all projects of Takari allowing deployment to the Central Repository and centralized plugin and configuration management.

Usage

Just add a parent segment with the latest version to your project

  <parent>
    <groupId>io.takari</groupId>
    <artifactId>takari</artifactId>
    <version>41</version>
  </parent>

To release your project you can use the usual Maven release process.

mvn release:prepare release:perform

This deploys the project to the Central Repository and hence the binaries are available whereever Central is available. Prior to that the staging repository needs to be closed and released on OSSRH.

SNAPSHOT version deployments emulating the full release build can be done with

mvn clean deploy -P takari-release

Binaries end up on https://oss.sonatype.org/content/repositories/snapshots/

The project uses the Takari Lifecycle for resources, compiler, jar, install and deploy replacement.

Build

As usual

mvn clean install

Release

Same as for usage of the project...

ca.vanzyl.concord

Versions

Version
0.0.3
0.0.2
0.0.1