Class AnnotationProcessorContext

    • Field Detail

      • initialized

        private boolean initialized
      • enumTransformationStrategies

        private java.util.Map<java.lang.String,​EnumTransformationStrategy> enumTransformationStrategies
      • elementUtils

        private javax.lang.model.util.Elements elementUtils
      • typeUtils

        private javax.lang.model.util.Types typeUtils
      • messager

        private javax.annotation.processing.Messager messager
      • disableBuilder

        private boolean disableBuilder
      • verbose

        private boolean verbose
    • Constructor Detail

      • AnnotationProcessorContext

        public AnnotationProcessorContext​(javax.lang.model.util.Elements elementUtils,
                                          javax.lang.model.util.Types typeUtils,
                                          javax.annotation.processing.Messager messager,
                                          boolean disableBuilder,
                                          boolean verbose)
    • Method Detail

      • initialize

        private void initialize()
        Method for initializing the context with the SPIs. The reason why we do this is due to the fact that when custom SPI implementations are done and users don't set proc:none then our processor would be triggered. And this context will always get initialized and the SPI won't be found. However, if this is lazily evaluated it won't be a problem, as in the SPI implementation module there won't be any processing done.
      • findAstModifyingAnnotationProcessors

        private static java.util.List<AstModifyingAnnotationProcessor> findAstModifyingAnnotationProcessors​(javax.annotation.processing.Messager messager)
      • getEnumTransformationStrategies

        public java.util.Map<java.lang.String,​EnumTransformationStrategy> getEnumTransformationStrategies()