[jakarta.ee-spec] artifactId redundency

[Emmanuel Bernard <ebernard@xxxxxxxxxx>]

Hi,

As part of the migration of Bean Validation to Jakarta, I saw that the
artifactId has redundancy with the groupId e.g.


<groupId>jakarta.el</groupId>
<artifactId>jakarta.el-api</artifactId>

<groupId>jakarta.interceptor</groupId>
<artifactId>jakarta.interceptor-api</artifactId>

Is there a constraint or is that the strongly recommended way?

My natural inclination would be to avoid the redundancy which will
ease the migration in quite a few cases e.g.

<groupId>jakarta.el</groupId>
<artifactId>el-api</artifactId>

<groupId>jakarta.interceptor</groupId>
<artifactId>interceptor-api</artifactId>

<groupId>jakarta.validation</groupId>
<artifactId>validation-api</artifactId>

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=548104#c31

Feedback welcome.

Emmanuel