kiskae / compile-testing-extension Goto Github PK

I know jfrog promises to keep jcenter forever but

When I use this extension to test my annotation processor, I notice that type annotations are ignored (annotations TYPE_USE)
For a given class :

public class TestToParse {

  private @MyAnnotation String field;

}

When using Elements provided by the extension, I get the right field but @MyAnnotation is missing.

Hi,
I've created an annotation processor and tried to test it with compile-testing and junit 5 (the default in my company) with no luck since it has a compile dependency on junit4.
Then I saw your pull request and I'm trying now with your extension.

But I keep receiving the message in title from eclipse and when running with maven no test is found.

Are you able to use Junit 5 to test your annotation processors ?

Basically afterAll lifecycle hook is invoked per "test container" and it will put the extension in an unexpected state. A small-ish fix might be to abandon the optimization of one compilation per test suite and just purely use one per test method. A more involved fix that retains the optimization will need to properly handle compilation termination

Hello,
since the original maintainers don't seem to be updating to junit 5 anytime soon.
I have published a fork of compile-testing here:
https://github.com/jbock-java/compile-testing
I have already made a couple of releases on maven central.
For the next release, I am planning to move to junit 5 and would like to add CompilationExtension.
Even though I don't fully understand yet what's going on with all that async stuff.
It looks like solid code and seems to work fine.
Would you be willing to contribute to the repo with a PR?