io.takari:appserver

Takari: The future of software delivery.

License

License

GroupId

GroupId

io.takari
ArtifactId

ArtifactId

appserver
Last Version

Last Version

0.0.7
Release Date

Release Date

Type

Type

takari-jar
Description

Description

Takari: The future of software delivery.

Download appserver

Dependencies

compile (26)

Group / Artifact Type Version
org.slf4j : slf4j-api jar 1.6.4
org.slf4j : slf4j-simple jar 1.6.4
javax.inject : javax.inject jar 1
com.google.inject : guice jar 4.0
com.google.inject.extensions : guice-servlet jar 4.0
com.google.inject.extensions : guice-multibindings jar 4.0
org.eclipse.sisu : org.eclipse.sisu.inject jar 0.3.3
com.google.guava : guava jar 19.0
io.takari.airlift : takari-swagger-bundle jar 0.1.2
io.takari.airlift : takari-swagger-core jar 0.1.2
javax.servlet : javax.servlet-api jar 3.1.0
org.eclipse.jetty : jetty-server jar 9.2.11.v20150529
org.eclipse.jetty : jetty-util jar 9.2.11.v20150529
org.eclipse.jetty : jetty-servlet jar 9.2.11.v20150529
org.eclipse.jetty : jetty-servlets jar 9.2.11.v20150529
org.eclipse.jetty : jetty-webapp jar 9.2.11.v20150529
org.eclipse.jetty : jetty-security jar 9.2.11.v20150529
org.eclipse.jetty : jetty-deploy jar 9.2.11.v20150529
javax.ws.rs : javax.ws.rs-api jar 2.0
io.takari.siesta : siesta-api jar 2.2.1
io.takari.siesta : siesta-server jar 2.2.1
io.takari.siesta : siesta-jackson2 jar 2.2.1
org.jboss.resteasy : resteasy-yaml-provider jar 3.0.18.Final
org.apache.shiro : shiro-core jar 1.3.2
org.apache.shiro : shiro-web jar 1.3.2
org.apache.shiro : shiro-guice jar 1.3.2

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>27</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

Versions

Version
0.0.7