Re: [ee4j-pmc] Action item: use of the jakarta groupId

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

On 9/17/18 9:57 AM, Ivar Grimstad wrote:
> I am a little curious as to why it should affect the GlassFish release...

RIs (using old terminology) will have to adopt this change as well and 
this may not be just about changing groupid of a dependency. For 
instance there is no direct dependency from glassfish to jws (jsr 181) 
and jax-ws apis (jsr 224) - these are currently being integrated into GF 
through project metro and its 'org.glassfish.metro:webservices-osgi' 
artifact, so at least metro project will have to update its build to 
adopt this change.

What about CDI or Bean Validation - or basically specs not originally 
owned by Oracle? Should or shouldn't group id be changed there? If not, 
wouldn't it be confusing for end users to see that some artifacts are 
under new 'jakartaee' group id while others still under 'old javax.*'?

thanks,
--lukas

> As David pointed out earlier, it is a one-line change in the spec 
> pom.xml files, so that is close to no overhead at all. And the 
> dependencies to the Eclipse-released specs must be changed anyway 
> because of the new version number, so there is close to no extra 
> overhead by changing the groupId to jakarta at the same time. It may 
> actually save some time since we will have the check that we have not 
> forgotten to update any dependencies since we can scan for 
> javax-groupIds...?
>
> Ivar
>
> On Mon, Sep 17, 2018 at 9:52 AM Steve Millidge (Payara) 
> <steve.millidge@xxxxxxxxxxx> wrote:
>
>     +1 in principle however I also have concerns on timing given the
>     next release of GlassFish will be a JavaEE 8 compatible release. Do
>     we switch now for the JavaEE 8 versions or later when the Jakarta EE
>     working group releases the specs?____
>
>     __ __
>
>     Shouldn’t the JavaEE 8 version of Eclipse GlassFish use the Oracle
>     released javax apis? ____
>
>     __ __
>
>     Steve____
>
>     __ __
>
>     *From:*ee4j-pmc-bounces@xxxxxxxxxxx
>     <mailto:ee4j-pmc-bounces@xxxxxxxxxxx> <ee4j-pmc-bounces@xxxxxxxxxxx
>     <mailto:ee4j-pmc-bounces@xxxxxxxxxxx>> *On Behalf Of *Dmitry Kornilov
>     *Sent:* 15 September 2018 12:20
>     *To:* EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx
>     <mailto:ee4j-pmc@xxxxxxxxxxx>>
>
>
>     *Subject:* Re: [ee4j-pmc] Action item: use of the jakarta groupId____
>
>     __ __
>
>     PMC, we should finish voting and make a formal statement about it. I
>     still don’t see that all PMC members are voted. ____
>
>     __ __
>
>     David: +1 (It was suggested by David, so I believe that he’s voting
>     +1)____
>
>     Ivar: ? (From your email I understand that you support it, but I
>     didn’t see your +1)____
>
>     Kevin: ? (From your email I understand that you support it, but I
>     didn’t see your +1)____
>
>     Mark: ?____
>
>     Steve: ?____
>
>     Dmitry: -1 (I support this change in general. My concern is about
>     deadlines and delaying GF release because of it. I will change my
>     vote if I get a confirmation from all vendors that they will push
>     their project leads to make this change smoothly.)____
>
>     __ __
>
>     — Dmitry____
>
>     __ __
>
>
>
>     ____
>
>         On 12 Sep 2018, at 20:20, David Blevins <dblevins@xxxxxxxxxxxxx
>         <mailto:dblevins@xxxxxxxxxxxxx>> wrote:____
>
>         __ __
>
>         Following up from the specification committee meeting.  We (PMC)
>         need to make sure all the specifications/api jars we release to
>         Maven Central are in the jakarta groupId.  Using JMS as an
>         example:____
>
>         __ __
>
>             -
>         https://github.com/eclipse-ee4j/jms-api/commit/8c6519d5544b49fa3fed672182d222f6c874aa54____
>
>         __ __
>
>         If you want an easy command to do it:____
>
>         __ __
>
>             $ perl -i -pe 's,Id>javax,Id>jakarta,g' pom.xml____
>
>         __ __
>
>         We'll need to re-release JAX-RS and make sure we add this to our
>         spreadsheet to track which projects have done it.____
>
>         __ __
>
>         Here's the document for reference with motivations on the change
>         in Maven coordinates:____
>
>         __ __
>
>           -
>         https://docs.google.com/document/d/1pm8fjNusxxecoI-9M-eYvnoTkmZTMraQETN7OeVyMnA/edit#heading=h.ma7xbsxflh33____
>
>         __ __
>
>
>
>         ____
>
>         -- ____
>
>         David Blevins____
>
>         http://twitter.com/dblevins
>         http://www.tomitribe.com____
>
>         310-633-3852 <tel:%28310%29%20633-3852>____
>
>         __ __
>
>         _______________________________________________
>         ee4j-pmc mailing list
>         ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
>         To change your delivery options, retrieve your password, or
>         unsubscribe from this list, visit
>         https://dev.eclipse.org/mailman/listinfo/ee4j-pmc____
>
>     __ __
>
>     _______________________________________________
>     ee4j-pmc mailing list
>     ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
>     To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
>
> --
>
> Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader
>
>
>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ee4j-pmc