Re: Assembly build error

Works for me. Thanks

> On Apr 20, 2026, at 12:14=E2=80=AFPM, Nikita Timofeev =
<[email protected]> wrote:
>=20
> It should be good now.
>=20
> On Mon, Apr 20, 2026 at 7:52=E2=80=AFPM Nikita Timofeev =
<[email protected]>
> wrote:
>=20
>> 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.
>>=20
>>=20
>> On Mon, Apr 20, 2026 at 5:33=E2=80=AFPM Andrus Adamchik =
<[email protected]>
>> wrote:
>>=20
>>> 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:
>>>=20
>>> $ 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]
>>>=20
>>>=20
>>> 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?
>>>=20
>>> 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.
>>>=20
>>> Andrus
>>>=20
>>>=20
>>>=20
>>>> On Apr 17, 2026, at 11:00=E2=80=AFAM, Michael Gentry =
<[email protected]>
>>> wrote:
>>>>=20
>>>> Hi Nikita,
>>>>=20
>>>> 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.
>>>>=20
>>>> Thanks,
>>>> mrg
>>>>=20
>>>>=20
>>>> On Tue, Apr 14, 2026 at 8:18=E2=80=AFAM Nikita Timofeev <
>>> [email protected]>
>>>> wrote:
>>>>=20
>>>>> 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.
>>>>>=20
>>>>> On Tue, Apr 14, 2026 at 2:37=E2=80=AFAM Andrus Adamchik =
<[email protected]>
>>>>> wrote:
>>>>>=20
>>>>>>> I just filed all my taxes
>>>>>>=20
>>>>>> Congrats! Which reminds me - I am still waiting for my numbers =
from
>>> the
>>>>>> accountants :)
>>>>>>=20
>>>>>>> so I have some free cycles now if there is
>>>>>>> anything I can do to help.
>>>>>>=20
>>>>>> 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 ?
>>>>>>=20
>>>>>> Andrus
>>>>>>=20
>>>>>>> On Apr 13, 2026, at 6:16=E2=80=AFPM, Michael Gentry =
<[email protected]>
>>>>> wrote:
>>>>>>>=20
>>>>>>> I just filed all my taxes, so I have some free cycles now if =
there is
>>>>>>> anything I can do to help.
>>>>>>>=20
>>>>>>> On Mon, Apr 13, 2026 at 5:08=E2=80=AFPM Andrus Adamchik =
<[email protected]
>>>>=20
>>>>>> wrote:
>>>>>>>=20
>>>>>>>> Not too many significant new features in M2 so far, though =
quite a
>>> few
>>>>>> bug
>>>>>>>> fixes. So yeah, we probably should do it.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> On Apr 13, 2026, at 4:45=E2=80=AFPM, Michael Gentry =
<[email protected]>
>>>>>> wrote:
>>>>>>>>>=20
>>>>>>>>> Is it time for a 5.0.M2?
>>>>>>>>>=20
>>>>>>>>> I noticed the M1 was released 2024-09-09 and that seems a long =
time
>>>>>>>> ago...
>>>>>>>>>=20
>>>>>>>>> Thanks,
>>>>>>>>> mrg
>>>>>>>>=20
>>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>> --
>>>>> Best regards,
>>>>> Nikita Timofeev
>>>>>=20
>>>=20
>>>=20
>>=20
>> --
>> Best regards,
>> Nikita Timofeev
>>=20
>=20
>=20
> --=20
> Best regards,
> Nikita Timofeev