> What's preventing those people from installing the Modeler? Honestly, enterprise policy, especially on Windows systems that were much more locked down than Macs. Running CM as a Maven plugin backdoored the app into their systems. I could also make them a cm.bat file or give them the mvn command to run. The latter was usually preferred as running a .bat file was against policy.
mrg On Sun, May 3, 2026 at 5:37 PM Andrus Adamchik <[email protected]> wrote: > I just whacked it yesterday :) Made Modeler internals a bit cleaner. > > > make it easier for people to run CM who didn't have it installed. > > I understand that this is the use case, but I can't relate to it. What's > preventing those people from installing the Modeler? > > A. > > > > On May 3, 2026, at 5:09 PM, Michael Gentry <[email protected]> wrote: > > > > I always created a cm.sh script in the root project directory to make it > > easier for people to run CM who didn't have it installed. > > > > The solution you show, for the Mac at least, works if you have CM > installed > > and a Mac. :-) > > > > I don't have any strong opinions, but if the burden of keeping the Maven > > plugin is minimal, I think I'd want to keep it. > > > > mrg > > > > On Sun, Apr 26, 2026 at 5:30 PM 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 > >
