Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Jakarta EE TCK Drive folder] Public Access Creation #3

Open
aeiras opened this issue Sep 4, 2020 · 5 comments
Open

[Jakarta EE TCK Drive folder] Public Access Creation #3

aeiras opened this issue Sep 4, 2020 · 5 comments

Comments

@aeiras
Copy link

aeiras commented Sep 4, 2020

Hola @ivargrimstad,

Can you please create a folder with public access in the Jakarta EE Community drive called Jakarta EE TCK?

After today's TCK call, we need the space to add the minutes from the public call. :) Thank you!

@keilw
Copy link
Member

keilw commented Sep 4, 2020

@aeiras @dblevins @ivargrimstad It's nice to help creating more TCK tests for future Jakarta EE versions, but is there a plan when TomEE might finally pass the existing TCK like all the other vendors that did it, some within a week after Jakarta EE 8 went Final? ;-)

@ivargrimstad
Copy link
Member

@aeiras I'm not the one responsible for maintaining this drive. It is handled by the marketing committee. As far as I know, they have appointed a group of maintainers.

@keilw
Copy link
Member

keilw commented Sep 8, 2020

So is this only for Marketing purposes? If not, how should it properly correlate with the actual Jakarta EE TCK repo?

@ivargrimstad
Copy link
Member

So is this only for Marketing purposes? If not, how should it properly correlate with the actual Jakarta EE TCK repo?

I don't think it is marketing. The Google Drive is maintained by the marketing committee.

@keilw
Copy link
Member

keilw commented Sep 8, 2020

Still keen to see, how this may work with the actual TCK e.g. automated tests and CI jobs like Jenkins? We had quite some bad experience with eager contributors writing JUnit tests or even TCK tests for JavaMoney and a lot of it had to be reverted because they did not understand the JSR enough, so I fear the test quality might be equally bad here unless it is also tested (automatically) in some form in the actual TCK environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants