> On Apr 8, 2021, at 12:12 AM, Zowalla, Richard > <[email protected]> wrote: > > (b) I only know the "jira-rest-java-client-core" provided by Atlassian > (see > https://mvnrepository.com/artifact/com.atlassian.jira/jira-rest-java-client-core/5.2.2 > ) - might be worth a try? Sadly, it will only work with the self-hosted > Jira Server instance. I do not know, if ASF is using the cloud-hosted > approach offered by Atlassian...
Apache does self-host, so we're good on that front assuming there aren't specific options that need to be enabled. I don't want to take too much of my time away from TCK work, but I'll see if I can create a small CLI for the jira-rest-java-client-core. We could use it to file JIRAs for the remaining TCK failures so we could divide and conquer on that too. If we could get even one or two more people helping there it'd make a huge difference. When we did the long march to Java EE 6 Web Profile compliance, we had about 4 or 5 of us working on it after hours in bursts, averaging what felt like about 1.5 FTEs at any given time. Every little bit helps. Even getting 2 or 3 more people doing one test each would have a very big impact. I think with the current status, no one knows who is working on what test so people are more inclined to stay out of the way. Some JIRAs can definitely fix/improve that. We actually couldn't file JIRAs for the remaining failing tests when we did Java EE 6 as the TCK at that time was commercially licensed and under NDA. We don't have that issue any more :) -David
smime.p7s
Description: S/MIME cryptographic signature
