CC007
CC007
I can confirm this issue happens in IntelliJ as well. It seems to happen due to gitflow waiting on a certain FutureTask in de AWT EventQueue thread, which obviously will...
We are now at java 15 going on 16 and Java 7 is now very much end-of-life. Isn't it time to include optionals into the standard java hamcrest library?
I just ran into the issue while trying to use an assumption with junit5 while using SMOG to generate the matchers. If it's needed I'm all for the existence of...
> > Are there any plans to update this chart for recent versions of k8s APIs and Helm 3? > > I don't think this project has active development.. Yup,...
The idea would be for those annotations to mimic the `--module`, `--module-path`, `--module-source-path` and `--processor-path` arguments to the compiler, while also defaulting the base of path arguments to the `src/test/resources`...
Alternatively, for the module path and processor path, you could maybe specify them by their groupId, artifactId and version: ```java @ExtendsWith(JavacExtension.class) @Module(name = "test", sourcePath = ".\\modules") @ModulePath("my.path.to:annotations:1.0-SNAPSHOT") @ProcessorPath("my.path.to:annotations:1.0-SNAPSHOT") @Processors(MyAnnotationProcessor.class)...
Maybe it would help to use GitFlow or GitHubFlow for the branching strategy, so that there's a specific release branch on which to make releases. That way your automation could...
Yea, right now stable acts a bit like the master branch and master like a develop branch. I don't think that there is anything wrong with that divide though, but...
I like it (though I might be biased 😁)
I feel like this mixes 2 features: - The ability to get references to specific types of elements that will be used by the annotation processor - The ability to...