Re: [jakarta.ee-spec] artifactId redundency

[Scott Stark <starksm64@xxxxxxxxx>]

We discussed needing to update the maven GAVs in a future release to realign names with the project renames. At that point updating repository names, GAVs, website links, etc can be done. For Jakarta EE 8 we just want to get it out the door with minimal impact to existing Java EE 8 users.

On Jul 15, 2019, at 6:10 AM, Kevin Sutter <sutter@xxxxxxxxxx> wrote:

Emmanuel,
Yep, that's the redundancy that was decided way back when...
https://wiki.eclipse.org/New_Maven_Coordinates

I'm not thrilled with it either, but that's what we did when we first published to maven.  It may look a little clumsy, but it works and we're not going to change it now.  :-)

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        Emmanuel Bernard <ebernard@xxxxxxxxxx>
To:        jakarta.ee-spec@xxxxxxxxxxx
Date:        07/15/2019 03:15 AM
Subject:        [EXTERNAL] [jakarta.ee-spec] artifactId redundency
Sent by:        jakarta.ee-spec-bounces@xxxxxxxxxxx

---

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