> On Apr 12, 2021, at 4:37 AM, Zowalla, Richard 
> <[email protected]> wrote:
> 
> Hi David,
> 
> thanks for the CLI (worked smoothly - but note for future users: do not
> try to create 174 subtasks at once without increasing http timeouts...)
> and sorry for the spam on commit@

We should definitely fix that.  Creating 174 subtasks is exactly the goal! :)

> I just created the related issue (TOMEE-3234) and all related sub-tasks 
> for the examples, which are not yet transformed to the server / api bom
> approach.

Very excellent!


-David

> Am Samstag, den 10.04.2021, 19:42 -0700 schrieb David Blevins:
>>> On Apr 8, 2021, at 12:52 PM, David Blevins <[email protected]
>>>> wrote:
>>> 
>>>> 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...
>>> 
>>> 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.
>> 
>> I've gone ahead and created nice little JIRA CLI
>> 
>> - https://twitter.com/dblevins/status/1381073496453775360
>> 
>> Did my best to document it so if you or anyone wanted to create tasks
>> around updating examples it should be a bit easier.
>> 
>> I did use it to create issues for all the remaining TCK failures, but
>> I'll post on that in a different thread.
>> 
>> 
>> -David
>> 
>> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to