Works for me. Thanks

> On Apr 20, 2026, at 12:14 PM, Nikita Timofeev <[email protected]> 
> wrote:
> 
> It should be good now.
> 
> On Mon, Apr 20, 2026 at 7:52 PM Nikita Timofeev <[email protected]>
> wrote:
> 
>> I see this failure too, I think it's from the upgrade of the Asciidoctor
>> Maven plugin sometime ago.
>> Will check that, probably some transitive dependency needs updating too.
>> 
>> 
>> On Mon, Apr 20, 2026 at 5:33 PM Andrus Adamchik <[email protected]>
>> wrote:
>> 
>>> BTW, while I was doing this massive brain surgery on the Modeler code
>>> base this weekend, I noticed that assembly profile builds fail with Ruby
>>> errors when generating PDFs:
>>> 
>>> $ mvn clean verify -Passembly,mac
>>> ...
>>> [ERROR] Failed to execute goal
>>> org.asciidoctor:asciidoctor-maven-plugin:3.2.0:process-asciidoc
>>> (generate-pdf-doc) on project getting-started-guide:
>>>  Execution generate-pdf-doc of goal
>>> org.asciidoctor:asciidoctor-maven-plugin:3.2.0:process-asciidoc failed:
>>> (LoadError) load error: stringio --
>>>  java.lang.ExceptionInInitializerError: null: no such method:
>>> org.jruby.RubyString.cat19(RubyString)RubyString/invokeVirtual: loader
>>> constraint violation:
>>>  when resolving method 'org.jruby.RubyString
>>> org.jruby.RubyString.cat19(org.jruby.RubyString)' the class loader
>>> 'bootstrap' of the current class,
>>>  java/lang/Object, and the class loader
>>> org.codehaus.plexus.classworlds.realm.ClassRealm @5635b14b for the method's
>>> defining class, org/jruby/RubyString,
>>>  have different Class objects for the type org/jruby/RubyString used in
>>> the signature (java.lang.Object is in module java.base of loader
>>> 'bootstrap';
>>>  org.jruby.RubyString is in unnamed module of loader
>>> org.codehaus.plexus.classworlds.realm.ClassRealm @5635b14b, parent loader
>>> 'bootstrap') -> [Help 1]
>>> 
>>> 
>>> Playing with asciidoc plugin versions didn't help. If this is
>>> reproducible for others, this will be a blocker for the release. Anyone
>>> else can confirm that it happens for them?
>>> 
>>> FWIW, I have an idea of a "dirty" fix... We don't need to include
>>> documentation in downloads in general and in PDF format in particular. Docs
>>> on the website should serve everyone's needs just fine.
>>> 
>>> Andrus
>>> 
>>> 
>>> 
>>>> On Apr 17, 2026, at 11:00 AM, Michael Gentry <[email protected]>
>>> wrote:
>>>> 
>>>> Hi Nikita,
>>>> 
>>>> I don't think there is an urgency to get M2 out, so if the outstanding
>>> PRs
>>>> make sense to include in M2, I think it is OK to wait on them.
>>>> 
>>>> Thanks,
>>>> mrg
>>>> 
>>>> 
>>>> On Tue, Apr 14, 2026 at 8:18 AM Nikita Timofeev <
>>> [email protected]>
>>>> wrote:
>>>> 
>>>>> Several PRs are waiting for me, but nothing is too critical, so we may
>>> go
>>>>> ahead with M3.
>>>>> Instructions are all good, I use them every time.
>>>>> 
>>>>> On Tue, Apr 14, 2026 at 2:37 AM Andrus Adamchik <[email protected]>
>>>>> wrote:
>>>>> 
>>>>>>> I just filed all my taxes
>>>>>> 
>>>>>> Congrats! Which reminds me - I am still waiting for my numbers from
>>> the
>>>>>> accountants :)
>>>>>> 
>>>>>>> so I have some free cycles now if there is
>>>>>>> anything I can do to help.
>>>>>> 
>>>>>> How about publishing the release. @Nikita - do you have anything in
>>> the
>>>>>> queue we'd need to deal with before M2 that can't be moved to M3? Also
>>>>>> anything missing in the release instructions at
>>>>>> https://cayenne.apache.org/dev/release-guide.html ?
>>>>>> 
>>>>>> Andrus
>>>>>> 
>>>>>>> On Apr 13, 2026, at 6:16 PM, Michael Gentry <[email protected]>
>>>>> wrote:
>>>>>>> 
>>>>>>> I just filed all my taxes, so I have some free cycles now if there is
>>>>>>> anything I can do to help.
>>>>>>> 
>>>>>>> On Mon, Apr 13, 2026 at 5:08 PM Andrus Adamchik <[email protected]
>>>> 
>>>>>> wrote:
>>>>>>> 
>>>>>>>> Not too many significant new features in M2 so far, though quite a
>>> few
>>>>>> bug
>>>>>>>> fixes. So yeah, we probably should do it.
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On Apr 13, 2026, at 4:45 PM, Michael Gentry <[email protected]>
>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>> Is it time for a 5.0.M2?
>>>>>>>>> 
>>>>>>>>> I noticed the M1 was released 2024-09-09 and that seems a long time
>>>>>>>> ago...
>>>>>>>>> 
>>>>>>>>> Thanks,
>>>>>>>>> mrg
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>>> --
>>>>> Best regards,
>>>>> Nikita Timofeev
>>>>> 
>>> 
>>> 
>> 
>> --
>> Best regards,
>> Nikita Timofeev
>> 
> 
> 
> -- 
> Best regards,
> Nikita Timofeev

Reply via email to