Nikita may have some insight on the errors. I could never build it locally, so I just send my changes straight to prod via CI/CD and then fix anything that doesn't look right 🤦♂️
> On Jun 24, 2026, at 4:42 PM, Michael Gentry <[email protected]> wrote: > > Trying to update the website, but when I run 'mvn' in cayenne-website, I > get this error: > > [INFO] [16:40:00] Finished 'scripts' after 3.64 s > [INFO] [16:40:00] Starting 'copy-js-map'... > [INFO] [16:40:00] Finished 'copy-js-map' after 63 ms > [INFO] > [INFO] events.js:183 > [INFO] throw er; // Unhandled 'error' event > [INFO] ^ > [INFO] Error: spawn > /Users/mrg/Projects/cayenne-website/src/main/assets/node_modules/jpegtran-bin/vendor/jpegtran > ENOENT > [INFO] at _errnoException (util.js:1024:11) > [INFO] at Process.ChildProcess._handle.onexit > (internal/child_process.js:190:19) > [INFO] at onErrorNT (internal/child_process.js:372:16) > [INFO] at _combinedTickCallback (internal/process/next_tick.js:138:11) > [INFO] at process._tickCallback (internal/process/next_tick.js:180:9) > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 6.083 s > [INFO] Finished at: 2026-06-24T16:40:00-04:00 > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > com.github.eirslett:frontend-maven-plugin:1.15.0:gulp (gulp) on project > cayenne-website: Failed to run task: 'gulp.js serve --host localhost --port > 3000 --prod_host https://cayenne.apache.org/' failed. > org.apache.commons.exec.ExecuteException: Process exited with an error: 1 > (Exit value: 1) -> [Help 1] > > I've tried changing -Ddev.port and -Ddev.host, but still hitting the same > error. Any ideas for updating this? > > Thanks, > mrg > > > On Wed, Jun 24, 2026 at 9:09 AM Andrus Adamchik <[email protected]> wrote: > >> Ah great. Thanks for doing that. >> >>> On Jun 24, 2026, at 8:29 AM, Michael Gentry <[email protected]> wrote: >>> >>> Yeah, I got the files published yesterday and was going to do the >>> announcement, website update, etc, today. >>> >>> On Wed, Jun 24, 2026 at 8:01 AM Andrus Adamchik <[email protected]> >> wrote: >>> >>>> We were actually thinking with Nikita to pre-build and commit the .exe >>>> launcher, so that Windows assemblies could be done on any platform. >>>> >>>> So I see the files are published. Let me try to find time and write the >>>> announcement. >>>> >>>> Thanks, >>>> Andrus >>>> >>>> >>>>> On Jun 22, 2026, at 2:26 PM, Michael Gentry <[email protected]> >> wrote: >>>>> >>>>> Excluding Windows... >>>>> >>>>> On Mon, Jun 22, 2026 at 2:16 PM Andrus Adamchik <[email protected]> >>>> wrote: >>>>> >>>>>> Congrats! And now we have more than one person who knows how to do it >> :) >>>>>> >>>>>>> On Jun 22, 2026, at 1:48 PM, Michael Gentry <[email protected]> >>>> wrote: >>>>>>> >>>>>>> Here's the final voting result: >>>>>>> >>>>>>> Andrus Adamchik (PMC): +1 >>>>>>> Nikita Timofeev (PMC): +1 >>>>>>> John Huss (PMC): +1 >>>>>>> Michael Gentry (PMC): +1 >>>>>>> >>>>>>> We'll get the release publicly published shortly. >>>>>>> >>>>>>> Thank you everyone! >>>>>>> >>>>>>> On Mon, Jun 22, 2026 at 1:10 PM John Huss <[email protected]> >> wrote: >>>>>>> >>>>>>>> I am +1 as well. >>>>>>>> >>>>>>>> On Mon, Jun 22, 2026 at 12:02 PM Michael Gentry < >> [email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I've updated my scripts that check for files that aren't properly >>>>>>>> licensed >>>>>>>>> and saw the two I missed before. I think these can be fixed for the >>>>>> next >>>>>>>>> release. >>>>>>>>> >>>>>>>>> Everything checks out on my end, so I'm also a +1. >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> mrg >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Jun 15, 2026 at 6:14 AM Nikita Timofeev < >>>>>>>> [email protected] >>>>>>>>>> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> +1 >>>>>>>>>> >>>>>>>>>> - sources parity - good >>>>>>>>>> - signatures - good (Windows assembly is signed with my key) >>>>>>>>>> - full build from sources - good >>>>>>>>>> - MacOS Modeler and MCP - runs on MacOS, JDK 25 >>>>>>>>>> - Generic Modeler and MCP - runs on MacOS, JDK 25 and 21 >>>>>>>>>> - Windows Modeler - runs on Windows 11, JDK 25 unsupported, only >> JDK >>>>>> 21 >>>>>>>>>> checked >>>>>>>>>> - RAT - missing headers in TestMcpServer.java and in >>>>>>>>>> org.slf4j.spi.SLF4JServiceProvider >>>>>>>>>> (we have headers in other providers). Good enough for the >> milestone >>>>>>>>>> release, it may be fixed later. >>>>>>>>>> - Staging Maven repo - good, verified with a demo project >>>>>>>>>> >>>>>>>>>> Also a note about the RAT: a bunch of new `.md` files are not >>>>>> excluded, >>>>>>>>>> need to fix config. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sun, Jun 14, 2026 at 8:01 PM Andrus Adamchik < >>>> [email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Ok, to back up my intuition on the license headers I am going to >>>> lean >>>>>>>>> on >>>>>>>>>>> the "lack of creativity" exception and "PMC judgement" clause in >>>> the >>>>>>>>> ASF >>>>>>>>>>> policy :) >>>>>>>>>>> >>>>>>>>>>> https://www.apache.org/legal/src-headers.html#faq-exceptions >>>>>>>>>>> >>>>>>>>>>> Andrus >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> On Jun 14, 2026, at 11:53 AM, Andrus Adamchik < >>>> [email protected] >>>>>>>>> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> I am +1. I added MCP checks to my previous checklist (and they >>>>>>>> pass). >>>>>>>>>>> Haven't tested Modeler on Windows. >>>>>>>>>>>> >>>>>>>>>>>> Noticed the Mac .dmg doesn't have the background image and our >>>>>>>> custom >>>>>>>>>>> layout. The contents of the .dmg are correct though, so this is >>>> not a >>>>>>>>>>> blocker either. (I've seen my own builds losing the layout on >> rare >>>>>>>>>>> occasions; never got to the bottom of it though). >>>>>>>>>>>> >>>>>>>>>>>> One of the unit tests was missing the Apache header (my fault, I >>>>>>>>> fixed >>>>>>>>>>> that already on the "past-M2" branch). I don't think this >>>>>>>> disqualifies >>>>>>>>>> the >>>>>>>>>>> release. This is an internal unit test, and is not expected to be >>>>>>>>>>> referenced or embedded by the end users in their code. Also the >> new >>>>>>>> .md >>>>>>>>>>> files don't have Apache headers, which I think is totally ok. >>>>>>>>>>>> >>>>>>>>>>>> Anyone has a different opinion on this? >>>>>>>>>>>> >>>>>>>>>>>> Andrus >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> On Jun 13, 2026, at 12:20 PM, Michael Gentry < >>>> [email protected] >>>>>>>>> >>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Hello everyone! >>>>>>>>>>>>> >>>>>>>>>>>>> Finally time for the 5.0 M2 release! >>>>>>>>>>>>> Thanks Nikita and Andrus for helping with my environmental >>>> issues! >>>>>>>>>>>>> Hopefully smoother in the future. (I'll have to give Windows >> the >>>>>>>>>> stinky >>>>>>>>>>>>> eye.) >>>>>>>>>>>>> >>>>>>>>>>>>> Release Notes: >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>> >> https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt >>>>>>>>>>>>> >>>>>>>>>>>>> Maven Repo: >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>> >> https://repository.apache.org/content/repositories/orgapachecayenne-1063/ >>>>>>>>>>>>> >>>>>>>>>>>>> Assemblies (Note the updated KEYS file there): >>>>>>>>>>>>> https://dist.apache.org/repos/dist/dev/cayenne/ >>>>>>>>>>>>> >>>>>>>>>>>>> Please evaluate the assemblies and cast your votes. >>>>>>>>>>>>> >>>>>>>>>>>>> Thanks, >>>>>>>>>>>>> mrg >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Best regards, >>>>>>>>>> Nikita Timofeev >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>> >>>> >> >>
