Have you considered switching the complete build to a single build tool?

[leonard84]

I've cloned the project, as I wanted to look at how difficult it would be to fix some small issues. However, building the project was more complicated than expected, due to the fact that I had to work with two build tools.

Have you considered unifying the complete build to a single build tool?
I've worked with both Maven and Gradle, so I'd be fine with either. (While I admit a preference for Gradle given that I work at the company that develops it, although I'm not working on it directly.)

If you look at https://github.com/gradle/cucumber-companion/ you can see how to build and publish a Maven plugin from a Gradle build.

[casid]

Hi @leonard84, I consider Gradle a neccessary evil, because people want to have a plugin to build jte projects with gradle. That's why there are so many integration test like Gradle projects in the project.

Whenever I start IntelliJ to work on the project, all the gradle project initialization is quite annoying, because it takes very long.

I don't plan to move away from maven for building the core of jte, because I prefer working on the project instead of the build tooling.