It took a while, but now we finally released version 0.7.0 containing the Gradle plugin for OpenFastTrace 3.0.2.
There were some issues that delayed the release:
The configuration of plugins changed in Gradle 6.0. The old API is deprecated and will be removed in Gradle 7.0, so we had to migrate to the new API. Calculating the test coverage of Gradle plugin integration tests requires plugin jacoco-gradle-testkit-plugin. With new Gradle versions the test task fails under Windows with exception message Failed to create MD5 hash for file content.
The previous blog post was published more than one year ago. That’s why it’s high time for an update. We where busy in the last weeks preparing some new releases for you!
# OpenFastTrace 3.0.2 This major release contains these changes:
The project now requires Java 11 for building and running. We re-structured the packages to have unique package names for each submodule. This is a precondition for Java 9 modules which we will introduce later.
We are happy to announce the latest release 2.3.5 of OpenFastTrace.
In this release we split the source code into sub-modules for api, importers, exporters etc. This has some advantages:
The dependencies of plugins are now enforced by the compiler. It is not possible that e.g. the specobject exporter depends on the specobject importer. Developers who want to extend OFT with custom importers or exporters only need add a dependency for the stable API module without all the other internal code.
To keep track of my working time I wrote a little time recording tool called White Rabbit. You can find it at https://github.com/itsallcode/white-rabbit.
Today I found a nice hint on a Cygwin forum on how to debug slow Bash auto-completion:
set -vx What that does is that it make all the steps visible that the completion uses to come to a result. No you just have to look if one sticks out especially.