Hi Henrique, Thanks for the feedback. I had thought the main use case would be folks who want to stay within the Maven toolset. I am still inclined to go ahead with CAY-2925 for the support footprint reasons that I mentioned, and hope that Maven-centric teams won't have much trouble switching.
BTW, if I remember correctly, Maven starts a generic cross-platform Modeler. Unless you are on Linux, a native version for Mac or Windows should provide a noticeably better UX. This is also a selling point :) Andrus > On Apr 27, 2026, at 1:44 AM, Henrique Gomes <[email protected]> wrote: > > I don’t feel strongly about it, and I understand it feels clunky. But the > nice thing to me, is not about starting an existing Modeler from the command > line. It is the “magic” of having it downloaded on demand, on whatever system > I happen to be in. It is also a small political thing when “selling” Cayenne > to other team members, not having to go and procure and install an app to > work on it. > All very small things so if it is decided to have it go, I will survive :-) > > Cheers, > > HG > >> On 26 Apr 2026, at 23:29, Andrus Adamchik <[email protected]> wrote: >> >> FYI: https://issues.apache.org/jira/browse/CAY-2925. Anyone feels strongly >> about the need for starting the Modeler from Maven? This always looked odd >> to me. Besides the following works just fine (on Mac): >> >> $ open CayenneModeler.app --args ~/path/to/cayenne-project.xml >> >> Andrus >
