[External] : Re: Proposal: Allow annotations on module directives
Alessandro Autiero
alautiero at gmail.com
Tue Nov 12 19:28:37 UTC 2024
Thanks for the insight.
Would collecting the data as I suggested in the previous message then be a
valuable data point in your opinion?
I can also think of trying to assess if maintainers of popular build tools
ever considered shipping a dialect that relied on module-info, but didn’t
do so as there wasn’t enough flexibility with the current annotations.
After all I’m aware that maven maintains a polyglot module which supports
other markup languages other than XML and scripting languages, so in my
opinion it’s not such a far fetched possibility.
On Tue, 12 Nov 2024 at 20:01, Alex Buckley <alex.buckley at oracle.com> wrote:
> On 11/12/2024 10:47 AM, Alessandro Autiero wrote:
> > I've included this possibility as last as I don't see any indication
> > that any similar work was done for JEP 120, where the only claimed
> > motivation
> >
> > Frequently-used idioms of programming with annotations in EE and
> > elsewhere awkwardly use a container annotation just to simulate the
> > ability to apply multiple annotations
> >
> > seems to be purely anecdotal.
>
> The claim about needing awkward container annotations came directly from
> a Java EE spec lead. Here's an example:
>
>
> https://docs.oracle.com/cd/E13222_01/wls/docs100/programming/annotate_dependency.html#wp1111955
>
> I forget the other examples, but the use cases are easily found:
>
>
> https://stackoverflow.com/questions/17000193/can-we-have-more-than-one-path-annotation-for-same-rest-method
>
>
> https://stackoverflow.com/questions/2513031/how-to-use-multiple-requestmapping-annotations-in-spring?noredirect=1&lq=1
>
> Alex
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/compiler-dev/attachments/20241112/5e4dd67f/attachment-0001.htm>
More information about the compiler-dev
mailing list