Re: M2?
Michael Gentry <[email protected]> Mon, 8 Jun 2026 12:48:25 -0400
| Newsgroups | gmane.comp.java.cayenne.devel |
|---|---|
| Message-ID | <CAOy5kzNAoR15w29nVwYGPirRN=rpSG_T8+Y3c-fu74xUbLoCZQ@mail.gmail.com> |
--000000000000a2774a0653c0c97c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
OK, installed Win10 in VB (a soul-crushing experience) along with Java,
Git, Maven, etc...
I was able to clone the repo (using PowerShell):
PS > git clone https://gitbox.apache.org/repos/asf/cayenne.git --branch
"cayenne-parent-5.0-M2" --depth 1 cayenne-m2-rel
This repeatedly fails, though:
PS > mvn clean install -P"assembly,src"
> Task :pluginUnderTestMetadata
> Task :processTestResources
> Task :testClasses
> Task :test
OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader
classes because bootstrap classpath has been appended
> Task :test
DbImportIT > simpleDbTaskSuccess() FAILED
org.junit.platform.commons.JUnitException at ArrayList.java:1596
Caused by: java.io.IOException at ForEachOps.java:184
DbImportIT > withProjectTaskSuccess() FAILED
org.junit.platform.commons.JUnitException at ArrayList.java:1596
Caused by: java.io.IOException at ForEachOps.java:184
DbImportIT > excludeRelDbTaskSuccess() FAILED
org.junit.platform.commons.JUnitException at ArrayList.java:1596
Caused by: java.io.IOException at ForEachOps.java:184
GradlePluginIT > gradleVersionsCompatibility() FAILED
org.junit.platform.commons.JUnitException at ArrayList.java:1596
Caused by: java.io.IOException at ForEachOps.java:184
36 tests completed, 4 failed
> Task :test FAILED
Any ideas what might cause the build to fail in the Gradle Plugin tests?
JDK 21 and latest Maven 3.9.
Thanks,
mrg
On Sun, Jun 7, 2026 at 8:46=E2=80=AFPM Michael Gentry <[email protected]>=
wrote:
> I found an old Win10 ISO. I'll try installing in VirtualBox, etc.
>
> On Sun, Jun 7, 2026 at 11:14=E2=80=AFAM Andrus Adamchik <aadamchik@gmail.=
com>
> wrote:
>
>> Yeah, I think this one actually requires Windows. In the past I'd run it
>> locally via VirtualBox. These days, I simply go to Azure and spin up a V=
M
>> for a few hours.
>>
>> Andrus
>>
>> > On Jun 6, 2026, at 5:14=E2=80=AFPM, Michael Gentry <[email protected]=
m> wrote:
>> >
>> > BTW...
>> >
>> > How do I do this step?
>> >
>> > # You will need to do this on Windows
>> > mvn clean package -Passembly,windows -DskipTests
>> >
>> > I've only got Mac and Linux.
>> >
>> >
>> > On Sat, Jun 6, 2026 at 4:37=E2=80=AFPM Michael Gentry <blacknext@gmail=
.com>
>> wrote:
>> >
>> >> OK, more updates...
>> >>
>> >> In my ~/.m2/settings.xml file, I changed:
>> >>
>> >> <id>apache.releases.https</id>
>> >>
>> >> to:
>> >>
>> >> <id>apache-releases</id>
>> >>
>> >> That allowed the mvn release:perform step to run and complete. I had
>> >> gotten apache.releases.https from one of the Apache pages on setting
>> up GPG
>> >> and my settings file.
>> >>
>> >> Starting the rest now...
>> >>
>> >> On Wed, Jun 3, 2026 at 9:20=E2=80=AFPM Michael Gentry <blacknext@gmai=
l.com>
>> wrote:
>> >>
>> >>> I switched to using the ASF Git and made it further, but am having
>> issues
>> >>> publishing the artifacts (public key) using mvn release:perform
>> step...
>> >>> I'll try to get that ironed out Thursday...
>> >>>
>> >>> mrg
>> >>>
>> >>>
>> >>> On Wed, Jun 3, 2026 at 8:16=E2=80=AFAM Nikita Timofeev <
>> [email protected]>
>> >>> wrote:
>> >>>
>> >>>> You can check if your GitHub ID is linked with your Apache account
>> in the
>> >>>> https://gitbox.apache.org self service. Other than that I don't hav=
e
>> >>>> many
>> >>>> ideas about what to check.
>> >>>> If your access continues to fail, I can proceed with this release
>> >>>> tomorrow.
>> >>>>
>> >>>> On Tue, Jun 2, 2026 at 10:11=E2=80=AFPM Michael Gentry <blacknext@g=
mail.com>
>> >>>> wrote:
>> >>>>
>> >>>>> I'm still getting errors about not having access to apache/cayenne
>> on
>> >>>>> GitHub. Should I try using the ASF Git repo? Or should someone els=
e
>> >>>> take
>> >>>>> over until I can resolve my environmental issues?
>> >>>>>
>> >>>>> On Mon, Jun 1, 2026 at 9:09=E2=80=AFPM Michael Gentry <blacknext@g=
mail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>>> Thanks for the tips, Nikita.
>> >>>>>>
>> >>>>>> I'm going to revert the changes and try again. I'll update with h=
ow
>> >>>> far I
>> >>>>>> get.
>> >>>>>>
>> >>>>>>
>> >>>>>> On Mon, Jun 1, 2026 at 8:20=E2=80=AFAM Nikita Timofeev <
>> >>>>> [email protected]>
>> >>>>>> wrote:
>> >>>>>>
>> >>>>>>> Hi Michael.
>> >>>>>>>
>> >>>>>>> The instructions should be good overall, I use them verbatim eve=
ry
>> >>>> time.
>> >>>>>>> What's definitely missing are the common problems and how to fix
>> >>>> them.
>> >>>>>>>
>> >>>>>>> Usually I go with `mvn release:rollback` first.
>> >>>>>>> If `rollback` can't run (likely because there is no release
>> >>>>> descriptor), I
>> >>>>>>> manually revert the commit performed by the `prepare` stage.
>> >>>>>>> Then check if the tags are still present and remove both local a=
nd
>> >>>>> remote
>> >>>>>>> if they exist.
>> >>>>>>> Once everything is reverted I start `release:prepare` again.
>> >>>>>>>
>> >>>>>>> If `release:perform` fails too, I try to repeat it first,
>> sometimes
>> >>>> it's
>> >>>>>>> just a nexus timeout or something.
>> >>>>>>> If the error persists I just repeat the same rollback -> prepare
>> ->
>> >>>>>>> perform
>> >>>>>>> cycle.
>> >>>>>>>
>> >>>>>>> Hope this helps. Tell me if you need some more info or support.
>> >>>>>>>
>> >>>>>>> On Mon, Jun 1, 2026 at 12:02=E2=80=AFAM Michael Gentry <
>> [email protected]
>> >>>>>
>> >>>>>>> wrote:
>> >>>>>>>
>> >>>>>>>> Sadly, still broken for me.
>> >>>>>>>>
>> >>>>>>>> On Sun, May 31, 2026 at 2:40=E2=80=AFPM Andrus Adamchik <
>> >>>> [email protected]>
>> >>>>>>>> wrote:
>> >>>>>>>>
>> >>>>>>>>> This worked for me, so I deleted the tag:
>> >>>>>>>>>
>> >>>>>>>>> git push origin :cayenne-parent-5.0-M2
>> >>>>>>>>> ...
>> >>>>>>>>> - [deleted] cayenne-parent-5.0-M2
>> >>>>>>>>>
>> >>>>>>>>> Maybe it will work now for you, that the old tag is gone?
>> >>>>>>>>>
>> >>>>>>>>> Andrus
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>> On May 31, 2026, at 2:31=E2=80=AFPM, Michael Gentry <
>> >>>> [email protected]>
>> >>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> This command failed on me:
>> >>>>>>>>>>
>> >>>>>>>>>> mvn release:prepare -DpreparationGoals=3D"clean install"
>> >>>>>>>>>> -DautoVersionSubmodules=3Dtrue
>> >>>>>>>>>>
>> >>>>>>>>>> I worked past the error and ran the command again, but it
>> >>>> failed
>> >>>>>>>> because
>> >>>>>>>>> it
>> >>>>>>>>>> couldn't create the tag because the tag already exists.
>> >>>> Somehow it
>> >>>>>>>>> created
>> >>>>>>>>>> the tag. So, I tried deleting the tag, but now I'm getting:
>> >>>>>>>>>>
>> >>>>>>>>>> [mrg@odin 14:15:58] ~/Projects/cayenne master> git push
>> >>>> origin
>> >>>>>>>>>> :cayenne-parent-5.0-M2
>> >>>>>>>>>> ERROR: Permission to apache/cayenne.git denied to mrg.
>> >>>>>>>>>>
>> >>>>>>>>>> Same error when I use:
>> >>>>>>>>>>
>> >>>>>>>>>> git push --delete origin cayenne-parent-5.0-M2
>> >>>>>>>>>>
>> >>>>>>>>>> Any suggestions? Or does someone else have a smoother path to
>> >>>> take
>> >>>>>>>> over?
>> >>>>>>>>>>
>> >>>>>>>>>> Thanks,
>> >>>>>>>>>> mrg
>> >>>>>>>>>>
>> >>>>>>>>>> PS. The tag got created when I had used HTTPS as the clone
>> >>>>> method. I
>> >>>>>>>>>> couldn't delete the tag that way, either (GitHub doesn't
>> >>>> support
>> >>>>>>>>> user/pass
>> >>>>>>>>>> credentials), so I deleted the repo and checked out using SSH=
,
>> >>>>>>> which is
>> >>>>>>>>>> when I get the permissions error.
>> >>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>> On Sun, May 31, 2026 at 1:29=E2=80=AFPM Michael Gentry <
>> >>>>> [email protected]
>> >>>>>>>>
>> >>>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>>> Hi Andrus, I'm working on it. Trying to resolve errors. I
>> >>>> suspect
>> >>>>>>> the
>> >>>>>>>>>>> release guide is a little bit out of date.
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Sun, May 31, 2026 at 9:20=E2=80=AFAM Andrus Adamchik <
>> >>>>>>> [email protected]>
>> >>>>>>>>>>> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>>> Hey Mike, wanted to check how things are going with the
>> >>>> release.
>> >>>>>>>> Eager
>> >>>>>>>>> to
>> >>>>>>>>>>>> start using M2 and committing more cleanup code :)
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> If you don't have time for it now, not a problem too. Just
>> >>>> let
>> >>>>> us
>> >>>>>>>> know.
>> >>>>>>>>>>>> Nikita and myself should be able to jump in.
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Andrus
>> >>>>>>>>>>>>
>> >>>>>>>>>>>>> On May 25, 2026, at 8:06=E2=80=AFPM, Michael Gentry <
>> >>>>> [email protected]
>> >>>>>>>>
>> >>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> I should be able to start it Tuesday afternoon.
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Sun, May 24, 2026 at 5:47=E2=80=AFPM Andrus Adamchik <
>> >>>>>>>> [email protected]>
>> >>>>>>>>>>>> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>>> I think at this point we are ready to release M2. It has =
a
>> >>>>> huge
>> >>>>>>> new
>> >>>>>>>>>>>> scope
>> >>>>>>>>>>>>>> - a complete new agentic coding stack.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Mike, do you still have time to prepare the release?
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Thanks,
>> >>>>>>>>>>>>>> Andrus
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>>> On Apr 17, 2026, at 11:00=E2=80=AFAM, 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=E2=80=AFAM 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=E2=80=AFAM 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 hav=
e
>> >>>>>>> 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=E2=80=AFPM, 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=E2=80=AFPM Andrus Adamch=
ik <
>> >>>>>>>>>>>> [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=E2=80=AFPM, 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
>> >>>>
>> >>>
>>
>>
--000000000000a2774a0653c0c97c--