User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
Well, first of all, it shouldn't use "JavaMail" anywhere in its
name. :-)
Since we haven't standardized any of this, it really doesn't matter
at this point, but you can look at what I did for Jakarta Mail if
you want.
Assuming you want to create a module that can be used as an
equivalent replacement for Jakarta Mail, it should be named
jakarta.mail. That's what clients of the module will request.
David Blevins wrote on 1/29/20 2:28 PM:
Related question, what module name should we use
for Geronimo JavaMail?
Why is the Jakarta Mail implementation allowed to use a
module name in the jakarta namespace? Isn't the
"jakarta.*" namespace reserved for specifications?
I always assumed it was, in which case the ".api" suffix
doesn't add any value & should be dropped.
Kind regards, Anthony
On 29/01/2020 17:49, Kevin Sutter wrote:
Lukas, We
are only trying to establish a convention for the
Specification (API) Projects. The implementations
might need to establish their own module naming
conventions.
For
the specific
case you referenced, isn't
that a quirk with Jakarta Mail? Under normal
conditions, there should be a clear separation between
the API and the Implementation.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx
Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
On 1/29/20 3:43 PM,
Kevin Sutter wrote:
> Is it a requirement that all of the Projects
use the OSGI
> Bundle-SymbolicName? (It probably is due to
the use of the maven bundle
> plugin, but I thought I would ask...)
Yes; GF is based on OSGi so whatever gets there,
needs to be OSGi bundle
and "The Bundle-SymbolicName manifest header is a
mandatory header."[1]
>
> Just to be clear with an example, I looked at
Servlet:
>
<bundle.symbolicName>jakarta.servlet-api</bundle.symbolicName>
>
> Thus, your proposed Automatic Module name would
be (given your proposed
> rules)?
> jakarta.servlet.api
>
> Are we good with this approach across the
Jakarta EE Projects?
no on my end as it may require implementation module
to be called API in
certain cases, ie https://github.com/eclipse-ee4j/mail/issues/409 has
some details. JDK does not use "api" in their module
names too. But if
majority wants it this way...