Could not find main class [modified]
-
Where is the class file com/omniide/OmniIDEApp within the items listed in your classpath, and are you sure the spelling is correct?
The best things in life are not things.
-
I'm not sure I am following... (Java isn't my strongpoint.) I don't set any environment variables myself, and I don't set any classpath myself either. I figured that the jar file (with the manifest and build file), would handle that for me.
RossouwDB wrote:
I don't set any classpath myself
The
-cp
option followed by a list of.jar
files is your classpath. You need to check that the class you are trying to invoke actually exists within one of your.jar
files and is under the specified path (i.e. package and class).The best things in life are not things.
-
RossouwDB wrote:
I don't set any classpath myself
The
-cp
option followed by a list of.jar
files is your classpath. You need to check that the class you are trying to invoke actually exists within one of your.jar
files and is under the specified path (i.e. package and class).The best things in life are not things.
Richard MacCutchan wrote:
-cp
option followed by a list of.jar
files is your classpathcrud, I knew but forgot that! Now I follow :-O The omniide is my "main" package, and the omniIDEApp is the entrypoint of my application. Everything is spelled correctly since I have even copied it as is from my Manifest file, but to no avail. Here is the actual code for my entrypoint class:
/*
* OmniIDEApp.java
*/package omniide;
import org.jdesktop.application.Application;
import org.jdesktop.application.SingleFrameApplication;/**
* The main class of the application.
*/
public class OmniIDEApp extends SingleFrameApplication {/\*\* \* At startup create and show the main frame of the application. \*/ @Override protected void startup() { show(new OmniIDEView(this)); } /\*\* \* This method is to initialize the specified window by injecting resources. \* Windows shown in our application come fully initialized from the GUI \* builder, so this additional configuration is not needed. \*/ @Override protected void configureWindow(java.awt.Window root) { } /\*\* \* A convenient static getter for the application instance. \* @return the instance of OmniIDEApp \*/ public static OmniIDEApp getApplication() { return Application.getInstance(OmniIDEApp.class); } /\*\* \* Main method launching the application. \*/ public static void main(String\[\] args) { launch(OmniIDEApp.class, args); }
}
This code is generated by NetBeans when the project is created. I am stumped as to the cause of this error! :wtf:
-
Richard MacCutchan wrote:
-cp
option followed by a list of.jar
files is your classpathcrud, I knew but forgot that! Now I follow :-O The omniide is my "main" package, and the omniIDEApp is the entrypoint of my application. Everything is spelled correctly since I have even copied it as is from my Manifest file, but to no avail. Here is the actual code for my entrypoint class:
/*
* OmniIDEApp.java
*/package omniide;
import org.jdesktop.application.Application;
import org.jdesktop.application.SingleFrameApplication;/**
* The main class of the application.
*/
public class OmniIDEApp extends SingleFrameApplication {/\*\* \* At startup create and show the main frame of the application. \*/ @Override protected void startup() { show(new OmniIDEView(this)); } /\*\* \* This method is to initialize the specified window by injecting resources. \* Windows shown in our application come fully initialized from the GUI \* builder, so this additional configuration is not needed. \*/ @Override protected void configureWindow(java.awt.Window root) { } /\*\* \* A convenient static getter for the application instance. \* @return the instance of OmniIDEApp \*/ public static OmniIDEApp getApplication() { return Application.getInstance(OmniIDEApp.class); } /\*\* \* Main method launching the application. \*/ public static void main(String\[\] args) { launch(OmniIDEApp.class, args); }
}
This code is generated by NetBeans when the project is created. I am stumped as to the cause of this error! :wtf:
Are you sure about the
com.
prefix in your class name:java -cp OmniIDE.jar;lib\AbsoluteLayout.jar;lib\appframework-1.0.3.jar;lib\beansbinding-1.2.1.jar;lib\swing-layout-1.0.4.jar;lib\swing-worker-1.1.jar com.omniide.OmniIDEApp
[edit]You can check this by running the command
jar -tvf
against the jar file that contains (or should contain) your main class.[/edit] [edit2]Or you could execute the.jar
file directly byjava -cp lib\AbsoluteLayout.jar;lib\appframework-1.0.3.jar;lib\beansbinding-1.2.1.jar;lib\swing-layout-1.0.4.jar;lib\swing-worker-1.1.jar -jar OmniIDE.jar
assuming your main class is in the
OmniIDE.jar
file. [/edit2]The best things in life are not things.
-
Are you sure about the
com.
prefix in your class name:java -cp OmniIDE.jar;lib\AbsoluteLayout.jar;lib\appframework-1.0.3.jar;lib\beansbinding-1.2.1.jar;lib\swing-layout-1.0.4.jar;lib\swing-worker-1.1.jar com.omniide.OmniIDEApp
[edit]You can check this by running the command
jar -tvf
against the jar file that contains (or should contain) your main class.[/edit] [edit2]Or you could execute the.jar
file directly byjava -cp lib\AbsoluteLayout.jar;lib\appframework-1.0.3.jar;lib\beansbinding-1.2.1.jar;lib\swing-layout-1.0.4.jar;lib\swing-worker-1.1.jar -jar OmniIDE.jar
assuming your main class is in the
OmniIDE.jar
file. [/edit2]The best things in life are not things.
-
Are you sure about the
com.
prefix in your class name:java -cp OmniIDE.jar;lib\AbsoluteLayout.jar;lib\appframework-1.0.3.jar;lib\beansbinding-1.2.1.jar;lib\swing-layout-1.0.4.jar;lib\swing-worker-1.1.jar com.omniide.OmniIDEApp
[edit]You can check this by running the command
jar -tvf
against the jar file that contains (or should contain) your main class.[/edit] [edit2]Or you could execute the.jar
file directly byjava -cp lib\AbsoluteLayout.jar;lib\appframework-1.0.3.jar;lib\beansbinding-1.2.1.jar;lib\swing-layout-1.0.4.jar;lib\swing-worker-1.1.jar -jar OmniIDE.jar
assuming your main class is in the
OmniIDE.jar
file. [/edit2]The best things in life are not things.
Richard MacCutchan wrote:
running the command
jar -tvf
against the jar file that contains (or should contain) your main classConfirms that
com.
is not needed, and that my main class is contained within the OmniIDE.jar file.Richard MacCutchan wrote:
Or you could execute the
.jar
file directlyDoes not work.
-
Richard MacCutchan wrote:
running the command
jar -tvf
against the jar file that contains (or should contain) your main classConfirms that
com.
is not needed, and that my main class is contained within the OmniIDE.jar file.Richard MacCutchan wrote:
Or you could execute the
.jar
file directlyDoes not work.
RossouwDB wrote:
Does not work.
Really not a helpful definition of a problem! What's the output of the
jar -tvf
command? Also what happens when you try with the-jar
option? Please show exact commands and exact output in all cases. PS: I do not use NetBeans but Eclipse, and I know there are some bits of framework stuff that NetBeans adds to your package so it may well be that you cannot run the final package outside of the NetBeans environment. However, why that would be so is anyone's guess.The best things in life are not things.
-
RossouwDB wrote:
Does not work.
Really not a helpful definition of a problem! What's the output of the
jar -tvf
command? Also what happens when you try with the-jar
option? Please show exact commands and exact output in all cases. PS: I do not use NetBeans but Eclipse, and I know there are some bits of framework stuff that NetBeans adds to your package so it may well be that you cannot run the final package outside of the NetBeans environment. However, why that would be so is anyone's guess.The best things in life are not things.
I don't know how and why, but now everything is working!! I was typing away, and doing a clean + build like I normally do,and when I tried to run it again, it bombarded me with error messages indicating that a lot of my packages could not be found! Stumped, I cleaned and built it a couple of times, but failed miserably when I want to run it (really odd, since it was running successfully a couple of seconds ago.) So, I located the "broken" package, and renamed it to the package NetBeans expected. Cleaned and built it, ran it - it worked. So i though I might give executing the application a shot, and it worked! It's really odd though, since NetBeans should have complained right from the start, but for some reason, it didn't.:confused: Anyway, thanks for your help.
-
RossouwDB wrote:
Does not work.
Really not a helpful definition of a problem! What's the output of the
jar -tvf
command? Also what happens when you try with the-jar
option? Please show exact commands and exact output in all cases. PS: I do not use NetBeans but Eclipse, and I know there are some bits of framework stuff that NetBeans adds to your package so it may well be that you cannot run the final package outside of the NetBeans environment. However, why that would be so is anyone's guess.The best things in life are not things.
Stop. that. NOW! This is no simple Java homework that's not running. Packaging and Deploying Desktop Java Applications with Netbeans[^] Check that, READ IT and follow the instructions instead of burning money online.
regards Torsten I never finish anyth...
-
Stop. that. NOW! This is no simple Java homework that's not running. Packaging and Deploying Desktop Java Applications with Netbeans[^] Check that, READ IT and follow the instructions instead of burning money online.
regards Torsten I never finish anyth...
-
Stop. that. NOW! This is no simple Java homework that's not running. Packaging and Deploying Desktop Java Applications with Netbeans[^] Check that, READ IT and follow the instructions instead of burning money online.
regards Torsten I never finish anyth...
-
This is no simple Java homework Netbeans should provide a functionality to export your project in a proper way. There is no need to build some strange stuff. That's time waisted.
regards Torsten I never finish anyth...
TorstenH. wrote:
This is no simple Java homework
It's NOT HOMEWORK. It's a project I am working on...
TorstenH. wrote:
Netbeans should provide a functionality to export your project in a proper way.
Clearly it's not always working so well, but I would still use NetBeans.
TorstenH. wrote:
There is no need to build some strange stuff
Why not??? What isn't strange in live? Clearly you are.... So am I!
TorstenH. wrote:
That's time waisted
No, actually it's not! I have learned something from this entire experience, so I would not say it's time wasted! **Note:**If you don't want to help people, and you want to attack them for some strange and peculiar reason, rather keep quiet! (Go read the guidelines: Insults, slap-downs and sarcasm aren't welcome. Let's work to help developers!)
-
TorstenH. wrote:
This is no simple Java homework
It's NOT HOMEWORK. It's a project I am working on...
TorstenH. wrote:
Netbeans should provide a functionality to export your project in a proper way.
Clearly it's not always working so well, but I would still use NetBeans.
TorstenH. wrote:
There is no need to build some strange stuff
Why not??? What isn't strange in live? Clearly you are.... So am I!
TorstenH. wrote:
That's time waisted
No, actually it's not! I have learned something from this entire experience, so I would not say it's time wasted! **Note:**If you don't want to help people, and you want to attack them for some strange and peculiar reason, rather keep quiet! (Go read the guidelines: Insults, slap-downs and sarcasm aren't welcome. Let's work to help developers!)
..That's what I said - this does not look like a simple homework-project that can be simply launched from the command line. Why would you even want to work on the command line? All you're asking for is to run it outside of your IDE. So I recommend to export the project in the given way and that's it. Netbeans will do what is is supposed to do - build your application. No need to waste hours of time on fuzzy command line arguments. Better get a nice ice cream and watch Netbeans do the build :cool:
regards Torsten I never finish anyth...