4

Hi Experts,   When trying to run my application localy I am greeted by this error message at the “bundle application” step. This happened when retrieving the correct studio pro version (9.24.1) and the application on a different device. I already tried deleting the local folder of the app. Also uninstalling and downloading studio pro again did nothing. Since the error message mentions the administration module I updated that as well with no luck. Any advice?   Initialized native services in: C:\Users\JUMP-DEV-110\.gradle\native Initialized jansi services in: C:\Users\JUMP-DEV-110\.gradle\native Received JVM installation metadata from 'C:\Program Files\Eclipse Adoptium\jdk-11.0.16.101-hotspot': {JAVA_HOME=C:\Program Files\Eclipse Adoptium\jdk-11.0.16.101-hotspot, JAVA_VERSION=11.0.16.1, JAVA_VENDOR=Eclipse Adoptium, RUNTIME_NAME=OpenJDK Runtime Environment, RUNTIME_VERSION=11.0.16.1+1, VM_NAME=OpenJDK 64-Bit Server VM, VM_VERSION=11.0.16.1+1, VM_VENDOR=Eclipse Adoptium, OS_ARCH=amd64} Found daemon DaemonInfo{pid=2976, address=[455ce446-0987-4706-9ae4-7a65b6f27096 port:49888, addresses:[/127.0.0.1]], state=Idle, lastBusy=1683279189393, context=DefaultDaemonContext[uid=70b0067e-f4fc-40ed-81b9-b02bdcb59327,javaHome=C:\Program Files\Java\jdk-11,daemonRegistryDir=C:\Users\JUMP-DEV-110\.gradle\daemon,pid=2976,idleTimeout=10800000,priority=NORMAL,daemonOpts=--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=windows-1252,-Duser.country=NL,-Duser.language=nl,-Duser.variant]} however its context does not match the desired criteria. Java home is different. Wanted: DefaultDaemonContext[uid=null,javaHome=C:\Program Files\Eclipse Adoptium\jdk-11.0.16.101-hotspot,daemonRegistryDir=C:\Users\JUMP-DEV-110\.gradle\daemon,pid=5688,idleTimeout=null,priority=NORMAL,daemonOpts=--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=windows-1252,-Duser.country=NL,-Duser.language=nl,-Duser.variant] Actual: DefaultDaemonContext[uid=70b0067e-f4fc-40ed-81b9-b02bdcb59327,javaHome=C:\Program Files\Java\jdk-11,daemonRegistryDir=C:\Users\JUMP-DEV-110\.gradle\daemon,pid=2976,idleTimeout=10800000,priority=NORMAL,daemonOpts=--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=windows-1252,-Duser.country=NL,-Duser.language=nl,-Duser.variant]   Looking for a different daemon... The client will now receive all logging from the daemon (pid: 13452). The daemon log file: C:\Users\JUMP-DEV-110\.gradle\daemon\7.6\daemon-13452.out.log Starting 19th build in daemon [uptime: 19 mins 13.641 secs, performance: 98%, non-heap usage: 28% of 256 MiB] Using 8 worker leases. Now considering [C:\Users\JUMP-DEV-110\Mendix\EbbenRooiApp-main\deployment, C:\Users\JUMP-DEV-110\Mendix\JumpPoker-main\deployment] as hierarchies to watch Watching the file system is configured to be enabled if available File system watching is active Starting Build Settings evaluated using settings file 'C:\Users\JUMP-DEV-110\Mendix\EbbenRooiApp-main\deployment\settings.gradle'. Projects loaded. Root project using build file 'C:\Users\JUMP-DEV-110\Mendix\EbbenRooiApp-main\deployment\build.gradle'. Included projects: [root project 'deployment'] > Configure project : Evaluating root project 'deployment' using build file 'C:\Users\JUMP-DEV-110\Mendix\EbbenRooiApp-main\deployment\build.gradle'. All projects evaluated. Task name matched 'clean-custom-classes' Task name matched 'compile' Task name matched 'package' Selected primary task 'clean-custom-classes' from project : Selected primary task 'compile' from project : Selected primary task 'package' from project : Tasks to be executed: [task ':clean-custom-classes', task ':compile', task ':package'] Tasks that were excluded: [] Resolve mutations for :clean-custom-classes (Thread[Execution worker Thread 2,5,main]) started. :clean-custom-classes (Thread[Execution worker Thread 2,5,main]) started. destroyer locations for task group 0 (Thread[included builds,5,main]) started. destroyer locations for task group 1 (Thread[included builds,5,main]) started. > Task :clean-custom-classes Caching disabled for task ':clean-custom-classes' because:   Build cache is disabled Task ':clean-custom-classes' is not up-to-date because:   Task has not declared any outputs despite executing actions. Resolve mutations for :compile (Thread[Execution worker Thread 2,5,main]) started. :compile (Thread[Execution worker Thread 2,5,main]) started. > Task :compile Caching disabled for task ':compile' because:   Build cache is disabled Task ':compile' is not up-to-date because:   No history is available. The input changes require a full rebuild for incremental task ':compile'. Full recompilation is required because no incremental change information is available. This is usually caused by clean builds or changing compiler arguments. Compiling with toolchain 'C:\Program Files\Eclipse Adoptium\jdk-11.0.16.101-hotspot'. Compiling with JDK Java compiler API. C:\Users\JUMP-DEV-110\Mendix\EbbenRooiApp-main\javasource\administration\proxies\Account.java:5: error: cannot access administration.proxies package administration.proxies; ^

asked 2023-05-05

2 answers