A follow-up, in case there are other jEnv users who may find it useful: jenv enable-plugin export
Will set JAVA_HOME. You'll have to restart your shell. If you run other jEnv commands (jenv shell 14) it'll set JAVA_HOME accordingly. Only need to run enable-plugin once. On Thu, Nov 18, 2021 at 8:14 AM Michael Gentry <blackn...@gmail.com> wrote: > Thanks Ari! > > I'd forgotten to try using the "open" command. I'm using jEnv to manage > JDKs and it doesn't set JAVA_HOME, so the "open" command fails. Turns out > you need to do this: > > jenv exec open /path/to/CayenneModeler.app > > The exec option does some PATH magic putting the currently selected JDK at > the front and then it works. > > > On Wed, Nov 17, 2021 at 6:00 PM Aristedes Maniatis <a...@ish.com.au.invalid> > wrote: > >> On OSX, I put this into my ~/.profile >> >> >> ---- >> export JAVA_11_HOME=$(/usr/libexec/java_home -v11) >> export JAVA_17_HOME=$(/usr/libexec/java_home -v17) >> >> >> alias java11='export JAVA_HOME=$JAVA_11_HOME' >> alias java17='export JAVA_HOME=$JAVA_17_HOME' >> ----- >> >> Then you can just type >> >> java11 >> >> >> And have Java11 as your default for all further commands in that shell. >> So this works: >> >> >> # java11 >> # open /Applications/CayenneModeler.app/ >> >> >> >> Ari >> >> >> >> >> >> >> On 18/11/21 5:28am, Andrus Adamchik wrote: >> > Yeah, when you run it manually from the shell, you select which JDK to >> use. When you start from Desktop, it depends on the native wrapper logic. >> > >> > BTW, just found the Jira and the mailing list discussion: >> > >> > >> > * https://issues.apache.org/jira/browse/CAY-2721 < >> https://issues.apache.org/jira/browse/CAY-2721> >> > * https://lists.apache.org/thread/p90898fsbjq6fv2lwvsw6vv1prob5ycr >> > >> > Andrus >> > >> >> On Nov 17, 2021, at 8:24 PM, Michael Gentry <blackn...@gmail.com> >> wrote: >> >> >> >> Oh, I meant to mention that the about dialog says it is using OpenJDK >> 1.8, >> >> but I suppose I only see that in the JAR version. >> >> >> >> I do have JDK 17 installed, so perhaps that is it. >> >> >> >> Thanks! >> >> >> >> >> >> On Wed, Nov 17, 2021 at 1:10 PM Andrus Adamchik <aadamc...@gmail.com> >> wrote: >> >> >> >>> Hi Mike, >> >>> >> >>> There's an issue with Java 17 and native Modeler components. Nikita is >> >>> testing a fix. >> >>> >> >>> So your problem is likely unrelated to Monterey. >> >>> >> >>> Andrus >> >>> >> >>> >> >>>> On Nov 17, 2021, at 7:51 PM, Michael Gentry <blackn...@gmail.com> >> wrote: >> >>>> >> >>>> Has anyone tried running Cayenne Modeler on macOS Monterey? >> >>>> >> >>>> I ran, or at least I tried, CM 4.2M3 to look at Lon's issue and CM >> >>> wouldn't >> >>>> run. Tried a version I downloaded from the web site and the version I >> >>> built >> >>>> previously for the 4.2M3 release cycle. Didn't see any messages in >> >>>> Console.app, but I didn't try to find other logs. I know the version >> I >> >>>> built previously ran on Big Sur at the time, otherwise I wouldn't >> >>>> have +1'ed it. >> >>>> >> >>>> Running the generic JAR works. >> >>>> >> >>>> Thanks, >> >>>> >> >>>> mrg >> >>> >> > >> >>
