Re: [EXTERNAL] cannot find or load main class - still - again

2023-02-16 Thread Thomas Kellerer

That's configured in the project properties in the "Compile" section

Christopher C. Lanz schrieb am 16.02.2023 um 18:48:

Hello, thanks for the suggestion, but I'm not sure: I inevitably run by typing 
"F6".

Chris Lanz


-

*From:* Thomas Kellerer 
*Sent:* Thursday, February 16, 2023 8:52 AM
*To:* users@netbeans.apache.org 
*Subject:* [EXTERNAL] Re: cannot find or load main class - still - again
This message did not originate from SUNY Potsdam or one of its trusted senders. 
Do not open attachments, click on links, or provide your credentials if the 
source is suspicious.


Are you using "Compile on Save"?

I have had occasional problems with that.

If you do use it, try to disable it and see if your problem goes away

Thomas


Christopher C. Lanz schrieb am 16.02.2023 um 14:27:

Hello,

  I am getting this error (output below) about every 4^th  time I run a (large) program for debugging. While 
clearing the cache _does_ solve the problem, so does the simple act of adding "//" to an early line 
in the main method, or sometimes removing "//"  or changing a "/* */" pair.

First question:

Does anyone have suggestions about why this happens, and/or how I can 
reduce/eliminate the occurrences of the error?

Second question:

Does anyone know how to get NetBeans support in the event the community is 
unable to help?

Thanks.

Chris Lanz

340 Dunn Hall, SUNY Potsdam

lan...@potsdam.edu

315 268 1547

--- exec-maven-plugin:1.5.0:exec (default-cli) @ Wdax ---

Error: Could not find or load main class mainPackage.Wdax

Caused by: java.lang.ClassNotFoundException: mainPackage.Wdax

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:764)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)

at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)

at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:370)

at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:351)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:215)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:171)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:163)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)

at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)

at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)

at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)

at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)

at jdk.internal.reflect.DirectMethodHandleAccessor.invoke 
(DirectMethodHandleAccessor.java:104)

at java.lang.reflect.Method.invoke (Method.java:578)

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

Re: [EXTERNAL] Re: cannot find or load main class - still - again

2023-02-16 Thread Christopher C. Lanz
Hello, thanks for the suggestion, but I'm not sure: I inevitably run by typing 
"F6".


Chris Lanz

340 Dunn Hall, SUNY Potsdam

lan...@potsdam.edu

315 268 1547





From: Thomas Kellerer 
Sent: Thursday, February 16, 2023 8:52 AM
To: users@netbeans.apache.org 
Subject: [EXTERNAL] Re: cannot find or load main class - still - again

This message did not originate from SUNY Potsdam or one of its trusted senders. 
Do not open attachments, click on links, or provide your credentials if the 
source is suspicious.


Are you using "Compile on Save"?

I have had occasional problems with that.

If you do use it, try to disable it and see if your problem goes away

Thomas


Christopher C. Lanz schrieb am 16.02.2023 um 14:27:
> Hello,
>
>  I am getting this error (output below) about every 4^th  time I run a 
> (large) program for debugging. While clearing the cache _does_ solve the 
> problem, so does the simple act of adding "//" to an early line in the main 
> method, or sometimes removing "//" or changing a "/* */" pair.
>
> First question:
>
> Does anyone have suggestions about why this happens, and/or how I can 
> reduce/eliminate the occurrences of the error?
>
> Second question:
>
> Does anyone know how to get NetBeans support in the event the community is 
> unable to help?
>
> Thanks.
>
> Chris Lanz
>
> 340 Dunn Hall, SUNY Potsdam
>
> lan...@potsdam.edu
>
> 315 268 1547
>
> --- exec-maven-plugin:1.5.0:exec (default-cli) @ Wdax ---
>
> Error: Could not find or load main class mainPackage.Wdax
>
> Caused by: java.lang.ClassNotFoundException: mainPackage.Wdax
>
> 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:764)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)
>
> at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)
>
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:370)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:351)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:215)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:171)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:163)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:81)
>
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:56)
>
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
>
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
>
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
>
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
>
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke 
> (DirectMethodHandleAccessor.java:104)
>
> at java.lang.reflect.Method.invoke (Method.java:578)
>
> 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: 1.187 s
>
> Finished at: 2023-02-16T08:14:23-05:00
>
> 
>
> Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec 
> (default-cli) on project Wdax: Command exec

Re: cannot find or load main class - still - again

2023-02-16 Thread Thomas Kellerer
Are you using "Compile on Save"?

I have had occasional problems with that.

If you do use it, try to disable it and see if your problem goes away

Thomas


Christopher C. Lanz schrieb am 16.02.2023 um 14:27:
> Hello,
>
>  I am getting this error (output below) about every 4^th  time I run a 
> (large) program for debugging. While clearing the cache _does_ solve the 
> problem, so does the simple act of adding "//" to an early line in the main 
> method, or sometimes removing "//" or changing a "/* */" pair.
>
> First question:
>
> Does anyone have suggestions about why this happens, and/or how I can 
> reduce/eliminate the occurrences of the error?
>
> Second question:
>
> Does anyone know how to get NetBeans support in the event the community is 
> unable to help?
>
> Thanks.
>
> Chris Lanz
>
> 340 Dunn Hall, SUNY Potsdam
>
> lan...@potsdam.edu
>
> 315 268 1547
>
> --- exec-maven-plugin:1.5.0:exec (default-cli) @ Wdax ---
>
> Error: Could not find or load main class mainPackage.Wdax
>
> Caused by: java.lang.ClassNotFoundException: mainPackage.Wdax
>
> 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:764)
>
> at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)
>
> at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)
>
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
> (DefaultBuildPluginManager.java:137)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
> (MojoExecutor.java:370)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
> (MojoExecutor.java:351)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:215)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:171)
>
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
> (MojoExecutor.java:163)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:117)
>
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
> (LifecycleModuleBuilder.java:81)
>
> at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
>  (SingleThreadedBuilder.java:56)
>
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
> (LifecycleStarter.java:128)
>
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)
>
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
>
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
>
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
>
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
>
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
>
> at jdk.internal.reflect.DirectMethodHandleAccessor.invoke 
> (DirectMethodHandleAccessor.java:104)
>
> at java.lang.reflect.Method.invoke (Method.java:578)
>
> 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: 1.187 s
>
> Finished at: 2023-02-16T08:14:23-05:00
>
> 
>
> Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec 
> (default-cli) on project Wdax: 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.
>
>
> For more information about the errors and possible solutions, please read the 
> following articles:
>
> [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
>
>
>
>

-
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



cannot find or load main class - still - again

2023-02-16 Thread Christopher C. Lanz
Hello,

 I am getting this error (output below) about every 4th time I run a (large) 
program for debugging. While clearing the cache does solve the problem, so does 
the simple act of adding "//" to an early line in the main method, or sometimes 
removing "//" or changing a "/* */" pair.

First question:

Does anyone have suggestions about why this happens, and/or how I can 
reduce/eliminate the occurrences of the error?

Second question:

Does anyone know how to get NetBeans support in the event the community is 
unable to help?

Thanks.


Chris Lanz

340 Dunn Hall, SUNY Potsdam

lan...@potsdam.edu

315 268 1547


--- exec-maven-plugin:1.5.0:exec (default-cli) @ Wdax ---

Error: Could not find or load main class mainPackage.Wdax

Caused by: java.lang.ClassNotFoundException: mainPackage.Wdax

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:764)

at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:711)

at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:289)

at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)

at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 
(MojoExecutor.java:370)

at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute 
(MojoExecutor.java:351)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:215)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:171)

at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:163)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)

at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)

at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)

at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)

at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:294)

at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)

at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)

at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)

at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)

at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)

at jdk.internal.reflect.DirectMethodHandleAccessor.invoke 
(DirectMethodHandleAccessor.java:104)

at java.lang.reflect.Method.invoke (Method.java:578)

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: 1.187 s

Finished at: 2023-02-16T08:14:23-05:00



Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:exec 
(default-cli) on project Wdax: 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.


For more information about the errors and possible solutions, please read the 
following articles:

[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException