io.takari.orchestra.docker:parent

Takari: The future of software delivery.

License	The Eclipse Public License, Version 1.0
Categories	Docker Container Virtualization Tools
GroupId	io.takari.orchestra.docker
ArtifactId	parent
Last Version	0.1.3
Release Date	Oct 28, 2016
Type	pom
Description	Takari: The future of software delivery.

Download parent

Filename	Size
parent-0.1.3.pom	1 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/io.takari.orchestra.docker/parent/ -->
<dependency>
    <groupId>io.takari.orchestra.docker</groupId>
    <artifactId>parent</artifactId>
    <version>0.1.3</version>
    <type>pom</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/io.takari.orchestra.docker/parent/
implementation 'io.takari.orchestra.docker:parent:0.1.3'

Gradle Kotlin

// https://jarcasting.com/artifacts/io.takari.orchestra.docker/parent/
implementation ("io.takari.orchestra.docker:parent:0.1.3")

Apache Buildr

'io.takari.orchestra.docker:parent:pom:0.1.3'

Apache Ivy

<dependency org="io.takari.orchestra.docker" name="parent" rev="0.1.3">
  <artifact name="parent" type="pom" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='io.takari.orchestra.docker', module='parent', version='0.1.3')
)

Scala SBT

libraryDependencies += "io.takari.orchestra.docker" % "parent" % "0.1.3"

Leiningen

[io.takari.orchestra.docker/parent "0.1.3"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

• base
• agent
• server
• ui

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...

Versions

Version
0.1.3 Oct 28, 2016
0.1.2 Oct 26, 2016
0.1.1 Sep 23, 2016
0.1.0 Sep 21, 2016
0.0.1 Sep 12, 2016