Eugene Lukash

```java List

the `javax.annotation.Nullable` applies just on methods/fields/params, so it will not be present on `TypeMirror`, and will be handled in `initSpecialAnnotations()` by `Element.getAnnotationMirrors()`. The code in initSpecialAnnotations, in TypeStringProvider etc is...

I've made some revisions/bugfixes about how type annotations are parsed/analysed. I can try to include a test for the example above to see how if works now/fix if it is...

made some debugging recently, so far it appears that if coming from another module, Javac would not give us the type annotations (regardless of the retention). Actually, help wanted to...

the corrected usage for your case would be ```java @InjectAnnotation(type= javax.persistence.Access.class, code="([[*]])", target = { InjectAnnotation.Where.ACCESSOR, InjectAnnotation.Where.FIELD }) or @InjectAnnotation(code="@javax.persistence.Access([[*]])", target = { InjectAnnotation.Where.ACCESSOR, InjectAnnotation.Where.FIELD }) ```

Another consideration is to create multi-annotation injection and precondition it on the presence of the annotation itself ```java @InjectAnnotation( type = Access.class, target = {InjectAnnotation.Where.FIELD, InjectAnnotation.Where.ACCESSOR}, ifPresent = true )...

I'm a bit out of the context here, so would ask for a solution, relevant PR welcome (asking anyone reading this). Thank you!

As discussed recently in another issue (#1288), there are some difficult problems with type level annotations on type arguments. `@AllowNulls`/`@SkipNulls` (from any package) on a collection might produce some signatures...

Thank you for the feature request! I think it would be really great to support this. I would definitely like such a feature if this would not require a lot...

@oehme I sympathize with your desire to defend the product and clear some FUD, and I stand corrected about Gradle not wrapping model object (just env and filer). Also apologies...