[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdi-dev] Annotation processing and TCK for next dev call
|
There is no Micronaut + Arquillian integration that I am aware of since Micronaut has no concept of deployments, JEE containers etc.
I'd personally like to spend a day trying to implement this solely in an Arquillian adapter, because I'm still convinced that 1. it can be done, 2. it's the best thing to do. Is there a Micronaut Arquillian adapter that I could try to modify?
LT
On the next dev call we should discuss the handing of annotation processing based implementation and the TCK. The latest attempt to introduce a two pass run mode:
Is still just introducing complexity that gets in the way of the normal mode of running annotation processors during the original compilation phase to produce the enhanced output.
Along the lines of what Denis has already suggested in that issues, annotation processor based implementations would just ignore the existing binary TCK artifact, download the source artifact, run their annotation processing phase as part of compilation, and then execute the TCK suite on the resulting output.
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
cdi-dev mailing list
cdi-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdi-dev
--
Graeme Rocher
