Eine Konferenz als Fremder besuchen

Wie ich die W-JAX 2019 besucht habe und als Fremder eine gute Zeit hatte schildere ich hier in einem Beitrag.

Is it worth reporting an obvious and trivial documentation error?

I reported and fixed a very small, obvious and trivial documentation error in an OSS project and it was worth it.

Read the full story on my GitHub page:

https://github.com/FrVaBe/blog/blob/master/2019-09-13_ObviousPullRequest/README.md

Open Source Elastic Stack - First Steps

Open Source Elastic Stack - First Steps

I evaluated the Open Source Elastic Stack and wrote some notes about it. You can find them on my GitHub account: 

https://github.com/FrVaBe/ElasticStack/tree/master/ElasticStackFirstSteps

How-To write and document a Maven Plugin

"Maven is - at its heart - a plugin execution framework; all work is done by plugins."

This quote is the start of the Maven Plugins documentation. Thus, if you want to customize your Maven build project you should think about using a special plugin. If no plugin for your task is available you have the possibility to write your own.

Java 9 - Multi-Release Jar Example

Java 9 offers the possibility to build a JAR file with a format that "allows multiple, Java-release-specific versions of class files to coexist in a single archive" (JEP 238: Multi-Release JAR Files).

Content of my Multi-Release Jar example artifact

I build a sample project to show how Multi-Release Jars can be build with Maven. You can find it here on my GitHub page.

First Steps With Degraph

A crucial part of implementing software components is to get your code free from unwanted package dependencies. But most of the time it is hard to get an overview of which code depends on each other. SonarQube is a great tool but unfortunately they dropped the Package Tangle Index analysis support (see 'Also worth noting' here). JDepend is another tool but I could not really get familiar with it (even not with the eclipse IDE integration). Thus I decided to try Degraph - a newer tool that I heard of some time ago.

Camunda BPM User Task with Timer Boundary Event to react on follow-up / due dates

User tasks (in general) often work with follow-up or due dates. Camunda BPM does support this by providing corresponding properties / members on the User Task BPMN. The Camunda API allows to filter user tasks by these dates so that due or overdue tasks can be found easily.

Beside the query filter also Timer Boundary Events on user tasks can be used to "detect" the maturity of a user task and to trigger an automatic action.

I implemented a working example to show the usage of timer boundary events on user tasks. You can find it at this GitHub location.

Have fun!