[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] TCK tests in the same repo as API andSpec
|
Ok, you may be right about that. :-)
As long as no one is planning to
do anything with the TCKs
right now, we can defer this until later. I just don't want lots of
people to rush ahead and start hacking on TCKs before there's a plan
in place. A few limited experiments, great, lots of hacking, not so
great.
Kevin Sutter wrote on 3/10/20 2:09 PM:
The way I
read Dmitry's
final statement is that this detailed plan does not have to be
in place
for Jakarta EE 9. These standalone TCKs are not a plan item for
Jakarta
EE 9. But, ... We still need to work on a plan so that when
we're done with Jakarta EE 9, we can hit the path quickly and
start developing
the TCKs for Jakarta EE 10.
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From:
Bill
Shannon <bill.shannon@xxxxxxxxxx>
To:
jakartaee-platform
developer discussions
<jakartaee-platform-dev@xxxxxxxxxxx>,
dmitry.kornilov@xxxxxxxxxx,
"'Andy Guibert'" <andy.guibert@xxxxxxxxx>
Date:
03/10/2020
14:06
Subject:
Re:
[jakartaee-platform-dev] [EXTERNAL] Re: TCK tests in the same
repo as API
andSpec
Sent
by: jakartaee-platform-dev-bounces@xxxxxxxxxxx
I was mostly with you until I got to
this:
It doesn't make sense to me to
create
a detailed plan now. It can be created later (after Jakarta EE 9
release)
when this effort is supported by other specs.
If you write the plan after the work is done, it's not a plan,
it's a record
of events.
We need the plan so people can see what's going to happen and
understand
what they need to do for their part of the work.
Also remember that we have a TCK Users Guide for each of the
TCKs.
Right now they're all pretty similar with some spec-specific
customizations.
Someone needs to figure out how that's going to work with the
new approach.
Maybe there's a general "How to Run a Junit and Arquillian Based
TCK"
that applies to all of them, and then a very short document for
each TCK
telling what needs to be configured for that TCK. Exactly what
you're
going to do here needs to be part of the plan.
The point of the plan is to describe what's going to be done and
use it
to coordinate the work as it happens. After the work is done,
you
need Users Guides and things like that that describe how to use
it.
"Internal" documentation describing how you created it and how
it works inside would be great, but hardly anyone produces such
documentation
anymore based on a mistaken belief that good code is self
documenting.
_______________________________________________
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://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!GqivPVa7Brio!IvFRqZh56vUZ8N1LBy-hXoexn-t51Twj8IBpDieiGDAVrviRKN5KdeKwd9XvcoT1dg$