Hi Gary,
On 2.12.2024 20:28, Gary D. Gregory wrote:
Just on the CP for one app tooling stack:
org.jetbrains.annotations.NotNull
org.jetbrains.annotations.Nullable
com.sun.istack.NotNull
com.sun.istack.Nullable
org.springframework.lang.NonNull
org.springframework.lang.Nullable
jakarta.annotation
pared to the other 13 kinds of annotations
> >>>> there) have some strong supporters[5].
> >>>> * keep the current _status quo_ for some annotations (e.g. `@InlineMe`
> >>>> and those OSGi versioning annotations that are not mirrored in the
> >>>>
o the `compile` scope of all
>>>>>> artifacts. In the near future nullability annotations will be all over
>>>>>> the place and JSpecify (compared to the other 13 kinds of annotations
>>>>>> there) have some strong supporters[5].
>>>>>&g
e some strong supporters[5].
>>>> * keep the current _status quo_ for some annotations (e.g. `@InlineMe`
>>>> and those OSGi versioning annotations that are not mirrored in the
>>>> Manifest),
>>>> * write a tool that removes the other annotation
keep the current _status quo_ for some annotations (e.g. `@InlineMe`
>> and those OSGi versioning annotations that are not mirrored in the
>> Manifest),
>> * write a tool that removes the other annotations from the class files.
>>
>> [5]https://jspecify.dev/about/
&g
>> * write a tool that removes the other annotations from the class files.
> >>
> >> [5]https://jspecify.dev/about/
> >
> > I decided to start implementing this proposal and I created PR #3228 to add
> > JSpecify as `compile` dependency. The PR still allows users (i
t are not mirrored in the
Manifest),
* write a tool that removes the other annotations from the class files.
[5]https://jspecify.dev/about/
I decided to start implementing this proposal and I created PR #3228 to
add JSpecify as `compile` dependency. The PR still allows users (include
OSGi and
