Common clients integrated with green threads (fibers)

Provides commonly-used HTTP, REST and other clients, integrated with with green threads (fibers) to minimize the performance impact in virtual environments

License	License The Apache Software License, Version 2.0
GroupId	GroupId es.upv.grycap.coreutils
ArtifactId	ArtifactId coreutils-fiber
Last Version	Last Version 0.2.0
Release Date	Release Date Jan 4, 2016
Type	Type jar
Description	Description Common clients integrated with green threads (fibers) Provides commonly-used HTTP, REST and other clients, integrated with with green threads (fibers) to minimize the performance impact in virtual environments
Project URL	Project URL https://github.com/grycap/coreutils
Project Organization	Project Organization GRyCAP

Download coreutils-fiber

Filename	Size
coreutils-fiber-0.2.0.pom
coreutils-fiber-0.2.0.jar	26 KB
coreutils-fiber-0.2.0-sources.jar	13 KB
coreutils-fiber-0.2.0-javadoc.jar	78 KB
Browse

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/es.upv.grycap.coreutils/coreutils-fiber/ -->
<dependency>
    <groupId>es.upv.grycap.coreutils</groupId>
    <artifactId>coreutils-fiber</artifactId>
    <version>0.2.0</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/es.upv.grycap.coreutils/coreutils-fiber/
implementation 'es.upv.grycap.coreutils:coreutils-fiber:0.2.0'

Gradle Kotlin

// https://jarcasting.com/artifacts/es.upv.grycap.coreutils/coreutils-fiber/
implementation ("es.upv.grycap.coreutils:coreutils-fiber:0.2.0")

Apache Buildr

'es.upv.grycap.coreutils:coreutils-fiber:jar:0.2.0'

Apache Ivy

<dependency org="es.upv.grycap.coreutils" name="coreutils-fiber" rev="0.2.0">
  <artifact name="coreutils-fiber" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='es.upv.grycap.coreutils', module='coreutils-fiber', version='0.2.0')
)

Scala SBT

libraryDependencies += "es.upv.grycap.coreutils" % "coreutils-fiber" % "0.2.0"

Leiningen

[es.upv.grycap.coreutils/coreutils-fiber "0.2.0"]

Dependencies

compile (4)

Group / Artifact	Type	Version
es.upv.grycap.coreutils : coreutils-logging	jar	0.2.0
co.paralleluniverse : quasar-core	jar	0.7.3
co.paralleluniverse : comsat-httpclient	jar	0.5.0
co.paralleluniverse : comsat-okhttp	jar	0.5.0

test (3)

Group / Artifact	Type	Version
es.upv.grycap.coreutils : coreutils-test	jar	0.2.0
net.jodah : concurrentunit	jar	0.4.2
org.mock-server : mockserver-integration-testing	jar	3.10.2

Project Modules

There are no modules declared in this project.

Core Utils: tools to facilitate the development of Java-based applications

The coreutils project contains several core libraries that deal with the following aspects of software development: providing common and extensible configuration across different application modules, executing ordered shutdown sequences when the JVM shutdowns, running tasks in a custom thread pool, allowing publish-subscribe-style communication between components without requiring them to explicitly register with one another, providing commonly-used clients (HTTP, REST) integrated with with green threads (fibers) to minimize the performance impact in virtual environments, installing logging bridges to unify logging across the entire application, maintaining testing groups and rules.

This project requires Java 1.8 or higher.

What is coreutils?

Coreutils is a toolkit for developing highly concurrent and distributed applications in Java. Every new release starts from the available technologies and choose carefully a core of components that is configured in coreutils to leverage their strengths and to simplify the development, testing and deployment of new Java applications.

Coreutils is an open-source software that can be used as an SDK or can be taken as a code base for developing custom applications.

What is not coreutils?

Coreutils is not a framework, nor a utility library. Coreutils puts a very thin layer on top of the underlying technologies, providing the necessary glue to integrate heterogeneous, already existing components into coherent applications. In many cases, coreutils will expose parts of the original APIs in especial to avoid data transfer from different data formats or storages. This make assuring backward compatibility impossible.

For Java frameworks and utility libraries take a look at the following (incomplete) list:

Spring Framework (http://projects.spring.io/spring-framework) is a full-featured framework with a focus on modern Java applications, in especial Spring Boot, Spring Data, Spring REST and Spring Cloud.
Jodd micro frameworks (http://jodd.org) is suitable for small and medium-sized projects where keeping a small memory footprint is critical.
Google Guava (https://github.com/google/guava) and Apache Commons (https://commons.apache.org) are the indisputable leader in the field of reusable Java components, providing common methods and behaviors that are widely used.

Latest release

Add a dependency on coreutils using Maven:

<dependency>
    <groupId>es.upv.grycap.coreutils</groupId>
    <artifactId>coreutils</artifactId>
    <version>0.2.0</version>
</dependency>

Using or extending coreutils

Despite Coreutils is an unopinionated toolkit, there are several aspects of the project configuration that deserve attention when using coreutils to develop a custom application. Coreutils includes testing groups and rules that can be used to isolate tests. These are used in the project itself to control the test output and to run the test groups in different build phases. Coreutils uses Maven profiles that are activated via environment properties.

These notes are also valid for extending coreutils.

Environment variables

grycap.tests.print.out set value to true to print tests output to the console and to write log messages to a temporary file. Otherwise, no messages are displayed.
grycap.deploy.release set value to true to release the project to the Maven Central repository. This requires proper configuration of the OSSRH credentials and access to the project's repository. The script ossrh-deploy.sh provides further information about deployment.

Run all tests, logging to the console

$ mvn clean verify -Dgrycap.tests.print.out=true |& tee /tmp/LOGFILE

To include only a specific submodule add the -pl to the arguments. For example, include the following to test only the submodule coreutils-common: -pl coreutils-common.

Run sanity and functional tests, logging to the console

$ mvn clean test -Dgrycap.tests.print.out=true |& tee /tmp/LOGFILE

Continuous integration

Continuous integration and code coverage are configured within the default Maven profile in the verify build phase.

$ mvn clean verify coreutils

Install to local Maven repository

$ mvn clean install coreutils

Examples (pending)

Spring Boot + Undertow

TO-DO list

Integrate naming tools.
HTTP2 client: get access to the underlying OkHttpClient instance by cloning the client.
Add more tests.

GRyCAP

Grid y Computación de Altas Prestaciones

Versions

Version
0.2.0 Jan 4, 2016