Re: Remove "cayenne-modeler-maven-plugin" in 5.0?

The fact that you can run otherwise forbidden arbitrary apps by =
launching them via Maven should already take you pretty far :)=20


> On May 3, 2026, at 10:29=E2=80=AFPM, Lon Varscsak =
<[email protected]> wrote:
>=20
> Andrus, I=E2=80=99m trying to work around Enterprise bank =
security=E2=80=A6any ideas? =F0=9F=98=89
>=20
> On May 3, 2026 at 5:13:31=E2=80=AFPM, Andrus Adamchik =
<[email protected]> wrote:
>=20
>> I do have a lot of empathy for people trying to bypass enterprise =
security
>> :) So here is a simple working recipe:
>>=20
>> --- pom fragment ---
>>=20
>> <dependencies>
>>   <dependency>
>>       <groupId>org.apache.cayenne.modeler</groupId>
>>       <artifactId>cayenne-modeler</artifactId>
>>       <version>${cayenne.version}</version>
>>   </dependency>
>> </dependencies>
>>=20
>> <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>
>>=20
>>=20
>> --- run command ----
>> $ mvn exec:java@run-modeler
>>=20
>>=20
>> It works with any version, past or future. We should just document =
this to
>> make it more accessible.
>>=20
>> Andrus
>>=20
>>=20
>> On May 3, 2026, at 7:10=E2=80=AFPM, Michael Gentry =
<[email protected]> wrote:
>>=20
>>=20
>>> What's preventing those people from installing the Modeler?
>>=20
>>=20
>> Honestly, enterprise policy, especially on Windows systems that were =
much
>>=20
>> more locked down than Macs. Running CM as a Maven plugin backdoored =
the app
>>=20
>> into their systems. I could also make them a cm.bat file or give them =
the
>>=20
>> mvn command to run. The latter was usually preferred as running a =
.bat file
>>=20
>> was against policy.
>>=20
>>=20
>> mrg
>>=20
>>=20
>>=20
>> On Sun, May 3, 2026 at 5:37=E2=80=AFPM Andrus Adamchik =
<[email protected]>
>> wrote:
>>=20
>>=20
>>> I just whacked it yesterday :) Made Modeler internals a bit cleaner.
>>=20
>>>=20
>>=20
>>>> make it easier for people to run CM who didn't have it installed.
>>=20
>>>=20
>>=20
>>> I understand that this is the use case, but I can't relate to it. =
What's
>>=20
>>> preventing those people from installing the Modeler?
>>=20
>>>=20
>>=20
>>> A.
>>=20
>>>=20
>>=20
>>>=20
>>=20
>>>> On May 3, 2026, at 5:09=E2=80=AFPM, Michael Gentry =
<[email protected]> wrote:
>>=20
>>>>=20
>>=20
>>>> I always created a cm.sh script in the root project directory to =
make it
>>=20
>>>> easier for people to run CM who didn't have it installed.
>>=20
>>>>=20
>>=20
>>>> The solution you show, for the Mac at least, works if you have CM
>>=20
>>> installed
>>=20
>>>> and a Mac. :-)
>>=20
>>>>=20
>>=20
>>>> I don't have any strong opinions, but if the burden of keeping the =
Maven
>>=20
>>>> plugin is minimal, I think I'd want to keep it.
>>=20
>>>>=20
>>=20
>>>> mrg
>>=20
>>>>=20
>>=20
>>>> On Sun, Apr 26, 2026 at 5:30=E2=80=AFPM Andrus Adamchik =
<[email protected]>
>>=20
>>> wrote:
>>=20
>>>>=20
>>=20
>>>>> FYI: https://issues.apache.org/jira/browse/CAY-2925. Anyone feels
>>=20
>>>>> strongly about the need for starting the Modeler from Maven? This
>> always
>>=20
>>>>> looked odd to me. Besides the following works just fine (on Mac):
>>=20
>>>>>=20
>>=20
>>>>> $ open CayenneModeler.app --args ~/path/to/cayenne-project.xml
>>=20
>>>>>=20
>>=20
>>>>> Andrus
>>=20
>>>=20
>>=20
>>>=20
>>=20
>>=20
>>=20