Yeah, all these little recipes are now very easy to retrieve if you know the right question to ask. Should've thought of it when I posted the original message in this thread.
Anyways, committed the snippet below to the docs. Andrus > On May 3, 2026, at 8:25 PM, Michael Gentry <[email protected]> wrote: > > You are cooking with gas now! > > On Sun, May 3, 2026 at 8:13 PM Andrus Adamchik <[email protected]> wrote: > >> I do have a lot of empathy for people trying to bypass enterprise security >> :) So here is a simple working recipe: >> >> --- pom fragment --- >> >> <dependencies> >> <dependency> >> <groupId>org.apache.cayenne.modeler</groupId> >> <artifactId>cayenne-modeler</artifactId> >> <version>${cayenne.version}</version> >> </dependency> >> </dependencies> >> >> <build> >> <plugins> >> <plugin> >> <groupId>org.codehaus.mojo</groupId> >> <artifactId>exec-maven-plugin</artifactId> >> <version>3.5.0</version> >> <executions> >> <execution> >> <id>run-modeler</id> >> <goals> >> <goal>java</goal> >> </goals> >> </execution> >> </executions> >> <configuration> >> <mainClass>org.apache.cayenne.modeler.Main</mainClass> >> </configuration> >> </plugin> >> </plugins> >> </build> >> >> >> --- run command ---- >> $ mvn exec:java@run-modeler >> >> >> It works with any version, past or future. We should just document this to >> make it more accessible. >> >> Andrus >> >> >>> On May 3, 2026, at 7:10 PM, Michael Gentry <[email protected]> wrote: >>> >>>> 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 >>>> >>>> >> >>
