Roland Huß

The most natural thing to do when building an MCP server is to mirror your existing API.

The previous post in The Flock series covered what happens when agents forget mid-run and confidently fill the gaps.

The init command for my Claude Code plugin needed a few things to happen in order: run a setup script, ask the user some configuration questions, apply the results.

The previous post in The Flock series covered what happens when agents get creative where they shouldn’t.

Every coding agent has its own context file.

You’ve seen this screen.

Your agent passed every guardrail test.

The 101 post covered working with one agent in one session, with a human watching.

The 101 post covered working with coding agents one-on-one.

You’re reading through a lengthy architecture proposal shared on a team channel, and something feels off.

The conversation was going well.

Everybody talks about prompt engineering.

Claude Code skills let you extend a coding agent with custom workflows, specialist knowledge, and automation.

The last post on this blog was about Jib, Google’s daemonless Java image builder.

As soon as Google’s blog post “Introducing Jib — build Java Docker images better” was online, all my channels went crazy about Jib.

Yesterday a blog post Using Docker from Maven and Maven from Docker by Kostis Kapelonis was published which gives some insights on the possible relationships between Docker and Maven.

I’m a big fan of the Camel Java DSL for defining Camel routes with a RouteBuilder.

As you might know, one of my Open Source babies is the one and only fabric8io/docker-maven-plugin (d-m-p).

Octobox is for sure one of my favourite tools in my GitHub centred developer workflow.

Since I got my first Amazon Echo end of last year, I love it.

Our Ansible Playbooks for installing Kubernetes on a Raspberry Pi Cluster have been constantly updated and are now using the awesome kubeadm.

From time to time people come to me and say: “I really would love Jolokia if only it would be RESTful”.

Now that some weeks has been passed we all had time to absorb the revised Java EE 8 proposal presented at Java One.

Let’s build a Raspberry Pi Cluster running Docker and Kubernetes.

rhuss/docker-maven-plugin is dead, long live fabric8io/docker-maven-plugin !

Dealing with multiple Docker registries is hard, mostly because the meta information where a image is located is part of a Docker image’s name, which is typically used as an identifier, too.

This screencast gives a live demo of the forthcoming JMX notification support in Jolokia 2.0.

I hope you all had a good start into 2016 and have charged all your batteries during the time of stillness.

When I had to create multiple Docker base images which only differ slightly for some minor variations I couldn’t avoid to feel quite dirty because of all the copying & pasting of Dockerfile fragments.

As you might know, Jmx4Perl is the mother of Jolokia.

Ok, you know Docker.

Building a Docker wormhole is easy.

The HTTP-JMX Bridge Jolokia allows easy access to JMX.

A health check is a useful technique for determining the overall operational state of a system in a consolidated form.

A local Maven repository serves as a cache for artifacts and dependencies, we all know this.

My docker-maven-plugin is undergoing a major refactoring.

While on the way of transforming the Jolokia integration test suite from a tedious, manual, half-a-day procedure to a full automated process I ran into and felt in love with Docker.

NSEnter is a nice way to connect to a running Docker container.

Recently I gave a Meetup talk for the Docker Munich Meetup Group which explained how Docker can help developers to improve integration tests and to ship applications.

Jolokia has configurable CORS support so that it plays nicely together with the Browser world when it comes to cross origin requests.

If you have ever sent or received mail messages via Java, chances are high that you have used JavaMail for this task.