Automatic module name

[ggam]

This is a first step before true modularization. We still depend on some projects which don't provide module names so I don't think we can go further right now.

[rdebusscher]

I doubt if we ever will be allowed to use the java prefix for module names from Oracle.

We need to wait with this (since we should never change this module name in the future) until there is an agreement around package names and module names between Oracle and Eclipse Foundation.

[ggam]

Based on @bshannon comments on jakartaee/servlet#204 (comment) and jakartaee/common-annotations-api#6 (review) I don't think we need to wait until the agreement to merge, and I understand that we could even integrate this into the first release, since it doesn't chance the API. I will have to ask the later to be completely sure.

[arjantijms]

Do note that there's the first release from the master branch, and the first release from the EE4J_8 branch.

The upcoming mandatory EE4J_8 release is the one that can't have API changes.

[ggam]

Would this considered an API change? It definitely changes some behaviour

[arjantijms]

@rdebusscher what is your vote on this issue? I'd like to resolve this one by either merging it as-is, or closing it if you vote -1, but I do need to know ;)

[rdebusscher]

Ok, we can put it in as proposed. But should come back to this name once there is an official statement about module names.

[arjantijms]

@rdebusscher okay, thx!