Thanks for digging into this, Richard! Agree with your prior statements about updating the README, branching for TomEE 8 and making TomEE 9 the master branch in the tomee-tck project.
> On Apr 24, 2022, at 11:14 PM, Zowalla, Richard > <[email protected]> wrote: > > Ok, I found it: > > - https://lists.apache.org/thread/sfbvz76c527wojym71csv72k8j2qrrg7 > > If we adjust the script to target the (released) ee9.1 tck (instead of > the snapshots), it will certainly help. (This was the script I had in > mint) Agree. Maybe it needs a new name as well so it's more clear that it can be used to create a fresh setup. > But while searching the list archive, I also found this post on happy > TCK work: > > - https://lists.apache.org/thread/vgthyd8d7rww2p398r9swx8y37mwxf9c > > Sadly the setup images from IntelliJ IDEA are gone (maybe you have them > somewhere, David?). Unfortunately, I don't have those images anymore. We can maybe describe the menu steps instead of showing images. Getting that on the website in the developer area would be good. > Perhaps we should provide a similar jakartaeetck-9.x installation via a > Git repository? > > Then we could adjust the "update" script and make it an "install" > script. The trick here is licensing of the TCK source code, which is EPL. Here's the source of truth on "is this license ok" questions: - https://www.apache.org/legal/resolved.html#weak-copyleft-licenses Effectively, we can use EPL in binary form. In source form it's ok in small amounts where it generally can't be avoided. An entire repository of EPL source code living under https://github.com/apache/ is likely not ok. It doesn't mean the idea is shot, but it does mean that repo would have to live outside the Apache org in github. > That would ease the necessary setup steps. Wdyt? Definitely agree it's a great idea. Perhaps we could create an org of our own? -David
smime.p7s
Description: S/MIME cryptographic signature
