Profiling still fails with the latest Open JDK: cd C:\Users\pjl\Source\VSP\platform-weather-data-ingester; JAVA_HOME=C:\\Users\\pjl\\Downloads\\openjdk-12.0.1\\jdk-12.0.1 M2_HOME=C:\\Users\\pjl\\Downloads\\apache-maven-3.6.1\\apache-maven-3.6.1 cmd /c "\"\"C:\\Users\\pjl\\Downloads\\apache-maven-3.6.1\\apache-maven-3.6.1\\bin\\mvn.cmd\" -Dexec.args=\"-agentpath:\\\"C:/Program Files/NetBeans-11.0/netbeans/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\Program Files\\NetBeans-11.0\\netbeans\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\\Users\\pjl\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\391249365\\org-netbeans-modules-profiler -classpath %classpath com.vaisala.platform.tools.weather.data.ingester.Main --vsp.sdk.observation.service.base-url=http://localhost:8080/api/ --ingester.retry-count=1 --server.port=8092 --spring.profiles.active=iceobs --iceobs.startOfSearch=2018-06-01T00:00:00Z --logging.level.com.vaisala.platform=DEBUG --iceobs.organizationIds[0]=317\" -Dexec.executable=C:\\Users\\pjl\\Downloads\\openjdk-12.0.1\\jdk-12.0.1\\bin\\java.exe -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans-11.0\\netbeans\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8 process-classes org.codehaus.mojo:exec-maven-plugin:1.5.0:exec\"" The syntax of the command is incorrect.
From: Lister Jonathan <jonathan.lis...@vaisala.com> Sent: Monday, 24 June, 2019 14:40 To: Luff,Chris <chris.l...@cerner.com> Cc: users@netbeans.apache.org Subject: RE: Profiling Maven project in NetBeans 11 fails with recent versions of Maven Thanks for the suggestion Chris. I tried Netbeans 11.0 with apache maven 3.6.2 and it still failed: cd C:\Users\pjl\Source\VSP\platform-weather-data-ingester; "JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_202" M2_HOME=C:\\Users\\pjl\\Downloads\\apache-maven-3.6.1\\apache-maven-3.6.1 cmd /c "\"\"C:\\Users\\pjl\\Downloads\\apache-maven-3.6.1\\apache-maven-3.6.1\\bin\\mvn.cmd\" -Dexec.args=\"-agentpath:\\\"C:/Program Files/NetBeans-11.0/netbeans/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\Program Files\\NetBeans-11.0\\netbeans\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\\Users\\pjl\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\391249365\\org-netbeans-modules-profiler -classpath %classpath com.vaisala.platform.tools.weather.data.ingester.Main --vsp.sdk.observation.service.base-url=http://localhost:8080/api/ --ingester.retry-count=1 --server.port=8092 --spring.profiles.active=iceobs --iceobs.startOfSearch=2018-06-01T00:00:00Z --logging.level.com.vaisala.platform=DEBUG --iceobs.organizationIds[0]=317\" -Dexec.executable=\"C:\\Program Files\\Java\\jdk1.8.0_202\\bin\\java.exe\" -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans-11.0\\netbeans\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8 process-classes org.codehaus.mojo:exec-maven-plugin:1.5.0:exec\"" The syntax of the command is incorrect. I guess I’ll try a different JDK next since I have the Oracle and you had success with Open JDK. From: Luff,Chris <chris.l...@cerner.com<mailto:chris.l...@cerner.com>> Sent: Friday, 21 June, 2019 16:04 To: Lister Jonathan <jonathan.lis...@vaisala.com<mailto:jonathan.lis...@vaisala.com>> Cc: users@netbeans.apache.org<mailto:users@netbeans.apache.org> Subject: Re: Profiling Maven project in NetBeans 11 fails with recent versions of Maven Have you tried 3.6.x? Profiling and Debugging works for me on 10, 11 and 11.1 with Adopt Open JDK 11. On 21 Jun 2019, at 14:39, Lister Jonathan <jonathan.lis...@vaisala.com<mailto:jonathan.lis...@vaisala.com>> wrote: We use Maven 3.5.2 and have configured NetBeans 11.0 to use the external maven via Tools | Options | Java | Maven and selecting the path to the Maven 3.2.2 folder. Most operations work just fine, but when trying to Profile a project I get: “The syntax of the command is incorrect.” The path of the actual command was: cd C:\Users\pjl\Source\VSP\platform-weather-data-ingester; "JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_202" M2_HOME=C:\\ProgramData\\chocolatey\\lib\\maven\\apache-maven-3.5.2 cmd /c "\"\"C:\\ProgramData\\chocolatey\\lib\\maven\\apache-maven-3.5.2\\bin\\mvn.cmd\" -Dexec.args=\"-agentpath:\\\"C:/Program Files/NetBeans-11.0/netbeans/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\Program Files\\NetBeans-11.0\\netbeans\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\\Users\\pjl\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\391249365\\org-netbeans-modules-profiler -classpath %classpath com.vaisala.platform.tools.weather.data.ingester.Main --vsp.sdk.observation.service.base-url=http://localhost:8080/api/ --ingester.retry-count=1 --server.port=8092 --spring.profiles.active=iceobs --iceobs.startOfSearch=2018-06-01T00:00:00Z --logging.level.com.vaisala.platform=DEBUG --iceobs.organizationIds[0]=317\" -Dexec.executable=\"C:\\Program Files\\Java\\jdk1.8.0_202\\bin\\java.exe\" -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans-11.0\\netbeans\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8 process-classes org.codehaus.mojo:exec-maven-plugin:1.5.0:exec\"" Switching back to the version of Maven bundled with NetBeans doesn’t work because our pom files are incompatible with the older Maven version: cd C:\Users\pjl\Source\VSP\platform-weather-data-ingester; "JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_202" M2_HOME=C:\\Users\\pjl\\Downloads\\incubating-netbeans-11.0-bin\\netbeans\\java\\maven cmd /c "\"\"C:\\Users\\pjl\\Downloads\\incubating-netbeans-11.0-bin\\netbeans\\java\\maven\\bin\\mvn.cmd\" -Dexec.args=\"-agentpath:\\\"C:/Program Files/NetBeans-11.0/netbeans/profiler/lib/deployed/jdk16/windows-amd64/profilerinterface.dll\\\"=\\\"C:\\Program Files\\NetBeans-11.0\\netbeans\\profiler\\lib\\\",5140,10 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=C:\\Users\\pjl\\AppData\\Local\\NetBeans\\Cache\\11.0\\mavencachedirs\\391249365\\org-netbeans-modules-profiler -classpath %classpath com.vaisala.platform.tools.weather.data.ingester.Main --vsp.sdk.observation.service.base-url=http://localhost:8080/api --ingester.retry-count=1 --server.port=8092 --spring.profiles.active=iceobs --iceobs.startOfSearch=2018-06-01T00:00:00Z --logging.level.com.vaisala.platform=DEBUG --iceobs.organizationIds[0]=317\" -Dexec.executable=\"C:\\Program Files\\Java\\jdk1.8.0_202\\bin\\java.exe\" -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans-11.0\\netbeans\\java\\maven-nblib\\netbeans-eventspy.jar\" process-classes org.codehaus.mojo:exec-maven-plugin:1.5.0:exec\"" Scanning for projects... [ERROR] Some problems were encountered while processing the POMs: Non-resolvable parent POM for com.vaisala.platform.tools:platform-weather-data-ingester:MASTER-SNAPSHOT: Could not transfer artifact com.vaisala.platform:platform-foundation:pom:2.1.0-b99 from/to vai-nexus (${nexus.repository.base}/${nexus.repository.releases}): Cannot access ${nexus.repository.base}/${nexus.repository.releases} with type default using the available connector factories: BasicRepositoryConnectorFactory and 'parent.relativePath' points at wrong local POM @ line 5, column 13 @ I found this bug report from 2017 that seems to be related: https://netbeans.org/bugzilla/show_bug.cgi?id=271059<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnetbeans.org%2Fbugzilla%2Fshow_bug.cgi%3Fid%3D271059&data=02%7C01%7CChris.Luff%40cerner.com%7Ca0706d32b349408fbd3f08d6f64ddd5b%7Cfbc493a80d244454a815f4ca58e8c09d%7C0%7C0%7C636967211623242872&sdata=x1DT7fpmC51HO6Q2o65O1msaRXEnfGsRdQS%2BbUnm9t0%3D&reserved=0> Is it likely that future releases of Netbeans will use a current release of maven? CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. Cerner Limited, Registered in England no 2519305, Registered Office 37 North Wharf Road, London W2 1AF.
