I would say that the location of the individual TCKs is still an open question... The Specs themselves will require a slightly more stringent licensing than the TCKs. Normally, an Eclipse project has a single license associated with it. Even if the content of the project has multiple github repos. So, I don't think it would be BAU to have a Spec Project contain a "spec repo" with one license and a "tck repo" with a different license.
Although... We are talking about the development of the respective Specs and TCKs, which all should be done under the EPL and/or Apache license. It's the distribution of the generated artifacts (pdf, binary, etc) that would be under a more restrictive license.
All of these license requirements and specs vs spec projects is clear as mud... :-)
-- Kevin
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
----- Original message -----
From: Scott Marlow <smarlow@xxxxxxxxxx>
Sent by: jakartaee-tck-dev-bounces@xxxxxxxxxxx
To: Bill Shannon <bill.shannon@xxxxxxxxxx>, jakartaee-tck developer discussions <jakartaee-tck-dev@xxxxxxxxxxx>
Cc:
Subject: Re: [jakartaee-tck-dev] discussion around jakartaee-tck/issues#51 and Turning TCK into a multi-dependency maven project
Date: Mon, Apr 22, 2019 9:29 AM
On 4/17/19 2:30 PM, Scott Marlow wrote:
> Another question related to [1], is about the moving of tests from the
> jakartaee-tck repo [2], to the respective SPEC API projects, so that the
> said tests can be maintained as part of the SPEC API project specific
> (standalone) TCK. Should the tests that require a Jakarta EE
> implementation to run, also be moved to the respective SPEC API project?
> Or does it make more sense to leave the Jakarta EE tests in the
> jakartaee-tck [2] repo?
Another possible path could be to move the tests that require a Jakarta
EE (full or web) implementation to run, to a new integration project for
each separate Jakarta EE spec API project, to be implemented/improved by
each separate Jakarta EE spec API project and to be consumed/used by the
jakartaee-tck project.
I'll be patient now and wait for input from others, but lets not wait
too long to discuss, as we have volunteers waiting to help I think via [1].
Scott
>
> Scott
>
> On 4/11/19 2:20 PM, Bill Shannon wrote:
>> Scott Marlow wrote on 4/11/19 6:53 AM:
>>> Hi,
>>>
>>> I have a few question for this mailing list, related to issues#51 [1].
>>>
>>> Where should we discuss the idea of moving standalone TCK tests, out
>>> of the
>>> jakartaee-tck [2] repo? Here on this mailing list or on the issue
>>> tracker [1]?
>>
>> I would say here on the mailing list.
>>
>>> My personal preference is to discuss on this email list, but I know from
>>> discussion on [1], that others will prefer using the issue tracker.
>>> The reason
>>> why I prefer using this mailing list, is because I think email does a
>>> better job
>>> of displaying a nested discussion, than (flat) github issues.
>>
>> I agree completely.
>>
>>> One reason to use
>>> [1], is so that others that aren't on this email list, can
>>> participate in this
>>> discussion.
>>
>> Anyone can subscribe to the mailing list, and they can view the
>> archives here:
>> https://www.eclipse.org/lists/jakartaee-tck-dev/
>>
>>>
>>> Scott
>>>
>>> [1] https://github.com/eclipse-ee4j/jakartaee-tck/issues/51
>>> [2] https://github.com/eclipse-ee4j/jakartaee-tck
>>> _______________________________________________
>>> jakartaee-tck-dev mailing list
>>> jakartaee-tck-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or
>>> unsubscribe from
>>> this list, visit
>>> https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
