Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] Module-info handling conventions for EE10

Ok, apologies, I thought that we had decided on that document as the base with the API_PACKAGE as the JMPS module name. I'll verify this on the platform list and update that document accordingly. 

On Nov 2, 2021 at 10:21:29 AM, Mark Thomas <markt@xxxxxxxxxx> wrote:

I read that document before I wrote my email.

NOTE: This document does not yet specify requirements for Java
platform module system names.

Given that:

- module-info is now being mandated; and
- module name is a required part of module-info;

where can I find rules / guidance / etc for the JPMS module name?

The projects I am involved with have automatic module names defined in
the manifest. We could just use those but I'd very much prefer to check
them against the rules / guidance / etc before doing so.


On 02/11/2021 15:59, Scott Stark wrote:

These the conventions that we came up with for EE since EE8:

Follow up with any questions.


On Nov 2, 2021 at 9:05:16 AM, Mark Thomas <markt@xxxxxxxxxx
<mailto:markt@xxxxxxxxxx>> wrote:


    I'm starting to look at this for the various specs I am involved in.

    Where can I find the rules / guidance / etc for what the module name
    should be?



    On 18/10/2021 15:49, Scott Stark wrote:
>     The last platform group meeting seemed to settle on the following
>     requirements for spec project API jars:
>     <>
>     <
>     <>>
>     If you are producing a Java 8 compatible service release for EE10, an
>     example of how to produce the expected format is given there.
>     _______________________________________________
>     jakartaee-spec-project-leads mailing list
>     jakartaee-spec-project-leads@xxxxxxxxxxx
>     <mailto:jakartaee-spec-project-leads@xxxxxxxxxxx>
>     To unsubscribe from this list, visit
>     <>

Back to the top