Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] artifactId redundency

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:

Yep, that's the redundancy that was decided way back when...

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)    

From:        Emmanuel Bernard <ebernard@xxxxxxxxxx>
Date:        07/15/2019 03:15 AM
Subject:        [EXTERNAL] [] artifactId redundency
Sent by:


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



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.





Feedback welcome.


Back to the top