JarCasting
JarCasting JarCasting

io.takari.orchestra.docker:parent

Takari: The future of software delivery.

License

License
Categories

Categories

Docker Container Virtualization Tools
GroupId

GroupId

io.takari.orchestra.docker
ArtifactId

ArtifactId

parent
Last Version

Last Version

0.1.3
Release Date

Release Date
Type

Type

pom
Description

Description

Takari: The future of software delivery.

Download parent

Filename Size
parent-0.1.3.pom 1 KB
Browse

How to add to project

<!-- 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>
// https://jarcasting.com/artifacts/io.takari.orchestra.docker/parent/
implementation 'io.takari.orchestra.docker:parent:0.1.3'
// https://jarcasting.com/artifacts/io.takari.orchestra.docker/parent/
implementation ("io.takari.orchestra.docker:parent:0.1.3")
'io.takari.orchestra.docker:parent:pom:0.1.3'
<dependency org="io.takari.orchestra.docker" name="parent" rev="0.1.3">
  <artifact name="parent" type="pom" />
</dependency>
@Grapes(
@Grab(group='io.takari.orchestra.docker', module='parent', version='0.1.3')
)
libraryDependencies += "io.takari.orchestra.docker" % "parent" % "0.1.3"
[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...

io.takari.orchestra.docker

Versions

Version
0.1.3
0.1.2
0.1.1
0.1.0
0.0.1