ca.vanzyl.concord.plugins:concord-plugin-testing

Takari: The future of software delivery.

License

License

GroupId

GroupId

ca.vanzyl.concord.plugins
ArtifactId

ArtifactId

concord-plugin-testing
Last Version

Last Version

0.0.8
Release Date

Release Date

Type

Type

takari-jar
Description

Description

Takari: The future of software delivery.

Download concord-plugin-testing

Dependencies

compile (8)

Group / Artifact Type Version
com.walmartlabs.concord : concord-sdk jar
com.walmartlabs.concord : concord-common jar
org.apache.commons : commons-compress jar
com.google.guava : guava jar
com.squareup.okhttp3 : okhttp jar
junit : junit jar
org.mockito : mockito-core jar
com.github.tomakehurst : wiremock jar

test (1)

Group / Artifact Type Version
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.plugins

Versions

Version
0.0.8
0.0.7
0.0.6
0.0.5
0.0.3
0.0.2
0.0.1