> On Apr 15, 2019, at 6:55 PM, Rob Tompkins <[email protected]> wrote: > > > >> On Apr 15, 2019, at 3:08 PM, Gary Gregory <[email protected]> wrote: >> >> On Mon, Apr 15, 2019 at 6:06 PM Bruno P. Kinoshita >> <[email protected]> wrote: >> >>> I think that should be fine. I think something similar already happened >>> in the past, but can't recall which component. >>> >>> On Tuesday, 16 April 2019, 9:58:43 am NZST, Rob Tompkins < >>> [email protected]> wrote: >>> >>> >>> >>>> On Apr 15, 2019, at 2:49 PM, Bruno P. Kinoshita < >>> [email protected]> wrote: >>>> >>>> >>>> Hi Scott, >>>> I believe it was a mistake. Had a look at 3.8 and we had published it >>> before. >>>> Just had a look at the vote thread, and it appears the javadocs jar was >>> not included in the process. Possibly something with our pom.xml and >>> plugins set up. >>>> >>>> @Rob, @Gary, is it possible to upload just the jar to an existing >>> release? >>> >>> Yes. My plan was to do just that. With a [LAZY][VOTE] on the staged >>> artifacts in nexus. Thoughts? >>> >> >> Since we approved the sources tagged and we are not changing those, I'd say >> we are OK to push out the javadoc files. > > This should be fixed now. It may take a little while for maven central to > pick up the changes. @Scott - many thanks for the catch there! > > Cheers, > -Rob
No problem. I appreciate the quick fix. Scott
