[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-tck-dev] discussion around jakartaee-tck/issues#51 and Turning TCK into a multi-dependency maven project
|
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?
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
