[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] [External] : Re: Jakarta TCK package naming convention
|
On 1/10/22 5:04 PM, Dmitry Kornilov
wrote:
I’m lost in this conversation and surprised
that we are jumping to voting so fast.
The vote ballot as currently written is now for EE 11 only and
for new TCKs being added to EE 11, which means the answer to the
original question that initiated this discussion is that the Batch
TCK does not need any changes (nor does other TCKs being added to
EE 10).
I couldn’t find the driver for this
change.
The driver was a question about packaging for the Jakarta Batch
TCK.
I thought the discussion was jumping towards adding a Platform
requirement for applications to not define classes in the
"jakarta" namespace but we didn't seem to get there. IMO, the
time to make such an application restriction would of been for EE
9 (since making such a change for EE 10 or 11 would be a breaking
change now, even if it has low likely impact on most
applications).
I believe that less renaming is better for
the platform. Renaming and especially renaming in TCKs is a
big task. Who is going to do this? I am not ready to assign
people to it. Last time we changed names for Maven artifacts
we introduced the package split problems we still suffering
with. So, if you ask me -> NO RENAMING!
IMO, if application classes are allowed to define classes in the
jakarta namespace, than TCKs should also be allowed to do the
same. If we add a breaking Platform SPEC change to EE 10 or 11 to
not allow applications to define classes in the jakarta namespace,
TCKs should then be updated (new + existing) to follow that same
rule.
Scott
-- Dmitry
P.S.
Also, I don’t think that it’s up to the
platform group to make this decision. TCKs are a part of
specifications, so it must go through the spec committee to
get approved.
Done. I thought from the conversation
thread, the package name of org.jakartatck.* might have
some complications. Anyway, I have added.
Can we add the org.jakartatck
option to this?
|
Having trouble viewing or
submitting this form?
|
|
|
|
|
|
|
I've
invited you to fill out a form:
|
|
|
Jakarta
TCK package naming
convention
|
|
|
For
all new Jakarta TCKs, we need a
naming convention. All TCKs for
Jakarta EE 10, the requirement
is not to use jakarta.*. From
Jakarta EE 11, the naming
convention must be used.
|
|
The
new Jakarta EE TCKs
from Jakarta EE 11
must use the
following naming
convention. Pick
your choice below.
-
( )
ee.jakarta.tck.[spec]
-
( )
tck.jakarta.[spec]
-
( )
org.eclipse.jakarta.tck.[spec]
|
|
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
--
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
