When we use the include directive to include another document we can must make sure the included document fits the levels of our main document.
For example the included document shouldn't have level 0 headings if the main document already contains a level 0 heading.
We can change the level offset in the main document before including another document.
This will change the heading levels for the included document so all heading rules are okay.
To change the level offset we use the document attribute leveloffset.
It is best to use a relative value, so if the included document also contains included document the output will still be okay and the heading rules still apply.
Alternatively we can use the leveloffset attribute for the include directive.
In the following sample document we include other files with a level 0 heading:
Continue reading →
Asciidoctor has built-in support for a couple of source syntax highlighting libraries like Coderay, Pygments, highlight.js and prettify.
In this post we learn how to use the Javascript library Prism to do the syntax highlighting for our source blocks.
Because Prism is a Javascript library we must remember this only works for the HTML backend of Asciidoctor.
In the following markup we have two source code listings in Java and Groovy:
Continue reading →
In Asciidoctor we can create a document attribute as a counter attribute.
The attribute is automatically incremented each time we use it in our markup.
We can choose to use numbers or characters.
Only latin characters from 'a' to 'z' or 'A' to 'Z' are allowed.
By default the counter will start at 1, but we can define another start value when we use the counter attribute for the first time.
To define a counter attribute we must prefix the attribute name with counter:.
Each time we use this syntax with the counter: prefix the value is incremented and displayed.
To only display the current value, without incrementing, we simply refer to the document attribute without the counter: prefix.
For example if we want to add a counter attribute with the name steps we would use the following markup in Asciidoctor: {counter:steps}.
Continue reading →
Having a Angular HTML5 single page application and a Spring Boot application, we would like to serve the complete Angular app from Spring Boot.
This blog shows you a couple simple steps to get everything up and running: run NPM from Gradle, integrate the Gradle frontend build in the main build and support HTML5 mode in the ResourceHandler of Spring Boot.
Create a subdirectory called frontend with the frontend code and build scripts (webpack, npm).
Let's assume our npm start and npm run watch output to the /frontend/dist/ directory.
First we need to make sure the frontend code is build when we run gradle build on our project.
We can use the plugin gradle-node-plugin for this.
Go ahead and create a /frontend/build.gradle file.
Continue reading →
In AngularJS, especially when you’re using a 'modern' Web Component like approach, you often have directives request the same information from your services multiple times.
Since we’d rather not do round-trips we don’t need to to save on server resources caching is our go-to solution.
In this post I will show two different approaches to caching resources: the built-in angular way using $resource and a home-grown solution.
Original post
Continue reading →
With Asciidoctor we can use text to describe a symbol in our markup.
The text is automatically transformed to a Unicode replacement.
For example if we use the text (C) it is converted to © which is the copyright symbol: ©.
In the following sample we see all the symbol replacements:
Continue reading →
Interesting links for week 41 2016:
Continue reading →
With the Gradle Wrapper task we can specify the name of the generated script files.
By default the names are gradlew and gradlew.bat.
The Wrapper task has the property scriptFile.
We can set a different value for this property to let Gradle generate the script files with a different name.
In the following example we use the value mvnw (they will be surprised the build is so fast... ;-)) as the value:
Continue reading →
One of my 2015 New Year’s resolutions was to finally turn my "I should write about this" notes into actual writing.
So here we are! My first ever blog post!
One of the things holding me back when it came to creating a blog is picking one of the many available blog frameworks, there’s just too many to choose from!
I wanted something that’s easy to use and easy to back-up.
Original post
Just this week I ran into JBake completely by accident (we were working with GVM and I just clicked all the links I didn’t know on that page to see what it was about).
Before I hadn’t even thought of using a static blog genererator but when I started reading about it, it made perfect sense!
Continue reading →
Sometime we need to define a project property in our Gradle build file for which the value must be evaluated later than the assignment.
We can do this in different ways in Gradle.
For example for a String type property we can rely on Groovy's support for lazy String evaluation.
If the property is of a different type we can use Closure to define the value.
The Closure code is not executed during the configuration phase directly, but we can write code to invoke the Closure at the right moment and get the value.
Finally we can use the afterEvaluate method of the Project class to define a lazy property.
Let's look at the different options we have with some code samples.
First we look at a lazy String property.
We illustrate this with an example of a multi-project build with the following layout:
Continue reading →
