Where do I specify maven debug keys
I am developing new SpringBoot application and trying to run for the first time within NB 18 and it fails without giving me any clue where the error occurred. I am getting following output: . ___ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' || .__|_| |_|_| |_\__, | / / / / =|_|==|___/=/_/_/_/ :: Spring Boot ::(v3.2.0) 2024-01-31 21:19:53.599 [METADATA-DEV] [main] [INFO ] com.visa.vms.etl.daemon.EtlDaemon : %PARSER_ERROR[enc] 2024-01-31 21:19:53.602 [METADATA-DEV] [main] [INFO ] com.visa.vms.etl.daemon.EtlDaemon : %PARSER_ERROR[enc] 2024-01-31 21:19:54.886 [METADATA-DEV] [main] [WARN ] o.s.c.a.AnnotationConfigApplicationContext : %PARSER_ERROR[enc] 2024-01-31 21:19:54.902 [METADATA-DEV] [main] [INFO ] o.s.b.a.l.ConditionEvaluationReportLogger : %PARSER_ERROR[enc] 2024-01-31 21:19:54.951 [METADATA-DEV] [main] [ERROR] o.s.b.d.LoggingFailureAnalysisReporter : %PARSER_ERROR[enc] Command execution failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404) at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:1000) at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:947) at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:471) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:342) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:330) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:175) at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:76) at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:163) at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:160) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:827) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272) at org.apache.maven.cli.MavenCli.main (MavenCli.java:195) at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104) at java.lang.reflect.Method.invoke (Method.java:577) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347) BUILD FAILURE Total time: 5.067 s Finished at: 2024-01-31T21:19:55-08:00 Failed to execute goal org.codehaus.mojo:exec-maven-plugin:3.1.0:exec (default-cli) on project etl_daemon: Command execution failed.: Process exited with an error: 1 (Exit value: 1) -> [Help 1] To see the full stack trace of the errors, re-run Maven with the -e switch. Re-run Maven using the -X switch to enable full debug logging. I can't figure out what kind of parser error it is. Tried to put those -e and -X switches on the command line in Run properties but they were not taken. Can someone please tell me how to find the cause of my problem. Thanks, Gary Greenberg Staff Software Engineer
changing wsimport used by the IDE
Hello! I need to bring online a mothballed NB 8/Java 8 java application Ant-based project that accesses a 3rd party webservice. I am presently on NB 15 IDE and Java 17 (those can't change right now). An option is to just run against Java 8, which works fine, but our other tools use Java 17, so I don't really want to have to deal with another Java runtime. Another option, as the project is Ant, is to add all the necessary Jakarta jars to the project for Jakarta support. That does work too, but with one issue. Whenever I clean and build, the import statements in the Generated Sources automatically created by the wsimport task all reference the javax.jws namespace, instead of the jakarta.jws namespace. I can change those import statements manually and then build, but my corrections are wiped out by any subsequent clean action, which automatically recreates the Generated Sources. In looking at the verbose output, it appears that NB IDE is using the wsimport bundled with the IDE, and it seems as though I need to tell the IDE to use the wsimport in the Jakarta package jars, or change some other setting in the IDE get the correct import statements in the Generated Sources, but I don't know how to do that. Any suggestions? Thank You! Joe Huber Standard Refrigeration LLC
Re: Changes of NB behavior with XML files
I tested it on an XML file created with NB20 and I did get the and options, as well as However - is your XML valid? I believe that attribute values need quotes around them, so xmlns="http://www.springframework.org/schema/beans"; not xmlns=http://www.springframework.org/schema/beans Maybe NB18 is more picky than NB12.5 was? Hope that helps, Peter On Tue, 30 Jan 2024 at 22:43, Greenberg, Gary wrote: > > I recently have to make some changes to the application that I have developed > about year and a half ago with NB 12.5 > > Now I am working with NB 18. > > Changes that I need to make involve Spring applicationContext.xml file. I > need to add entries to table. > > I do have in this file beans definition reference: > > http://www.springframework.org/schema/beans > >xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance > >xmlns:util=http://www.springframework.org/schema/util > xsi:schemaLocation=" > > http://www.springframework.org/schema/beans > http://www.springframework.org/schema/beans/spring-beans.xsd > > http://www.springframework.org/schema/util > http://www.springframework.org/schema/util/spring-util.xsd";> > > > > Before, when I type in “<” inside the map, Netbeans gave me a prompt choice: > , or and > if I choose it did prompt me for key and value. > Now, NB only give me one prompt . > I am wondering what is causing this reduction of functionality. Was it a bug > introduced or it was intentional? > > IMHO, intentional reduction of functionality does not improve popularity of > my favorite IDE. > > Has it been fixed in v.20 or v.21? Shall I go through paperwork and approval > hustle to install newer version or switched to > company approved IntellJ? > > Gary Greenberg > > Staff Software Engineer > > - To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
