Ok, so that would give us:
jakarta.tutorial:tutorial
jakarta.tutorial:tutorial-examples
jakarta.firstcup:firstcup
jakarta.firstcup:firstcup-examples
Or should the artifactId for the examples just be "examples"?
Kevin Sutter wrote on 2/8/19 8:54 AM:
All of the existing APIs are
using jakarta.*
as the groupId. Shouldn't we be consistent with these
tutorials?
So, we could use jakarta.tutorial and jakarta.firstcup. And,
use the artifactId to differentiate between jakarta.tutorial and
jakarta.tutorial-examples?
Something along those lines?
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java 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:
"Guillermo González
de Agüero" <z06.guillermo@xxxxxxxxx>
To:
Bill Shannon
<bill.shannon@xxxxxxxxxx>
Cc:
jakartaee-platform
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Date:
02/08/2019 01:40 AM
Subject:
Re:
[jakartaee-platform-dev]
move tutorials from GlassFish to Jakarta EE platform project?
Sent by:
jakartaee-platform-dev-bounces@xxxxxxxxxxx
Then I would either name them
ee.jakarta.tutorial[.examples]
and ee.jakarta.firstcup[.examples], or I'd rename the
jakartaee-tutorial[-examples]
to jakartaee-docs[-examples] and name its corresponding
artifacts ee.jakarta.docs[.examples],
to keep names consistent.
On Fri, Feb 8, 2019 at 8:26 AM Bill Shannon <bill.shannon@xxxxxxxxxx>
wrote:
There are four repositories:
jakartaee-tutorial
jakartaee-tutorial-examples
jakartaee-firstcup
jakartaee-firstcup-examples
Guillermo González de Agüero wrote on 2/7/19 11:07
PM:
What about ee.jakarta.tutorial to match the
repository
name? Other valid option is to rename the repository to
jakartaee-docs.
On Thu, Feb 7, 2019 at 11:47 PM Bill Shannon <bill.shannon@xxxxxxxxxx>
wrote:
The tutorials have been moved. I'm in the process
of doing some cleanup.
What Maven groupId should be used for the tutorials?
We're not publishing any of these artifacts to maven so it
doesn't *really*
matter, as far as I can tell.
Choices are:
ee.jakarta.docs
org.eclipse.ee4j
org.eclipse.ee4j.docs
something else
We can't use org.jakartaee because we don't own jakartaee.org.
Unless I hear objections, I'm going to use ee.jakarta.docs.
We might consider using ee.jakarta.api for the Jakarta EE API
artifacts
in the future.
Bill Shannon wrote on 1/30/19 1:52 PM:
> The Java EE Tutorial and First Cup of Java EE tutorials
(and corresponding
> sample code) have been contributed to the GlassFish
project.
Should we move
> them to the platform project?
>
> The tutorials do have some GlassFish-specific parts where
they describe
how
> to set up GlassFish so you can actually run the sample
code, but their
main
> purpose is to teach people the programming model and APIs.
>
> Should we rename the repositories from (e.g.)
glassfish-tutorial to
> jakartaee-tutorial and associate them with this platform
project instead
> of the GlassFish project?
>
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
|