Ndtyjky

The problem is most likely with your run configuration.

• Go to your Class that contains the main(String args) method you wish to automatically run
  when the jar is called from the command line


• Right-click->Run As...->Application


• Make sure it runs to your satisfaction


• Now go through the export process as before, selecting the newly created launch configuration.

The last step is key.

I found another solution.

I found that there's a bug in JDK 9.

I solved it by downgrade to JDK 8(1.8.1)

Try this, this is the way to create a jar or runnable jar in eclipse, all your external libraries in the project will be included

File -> Export-> Java ->Runnbale JAR file



Launch configuration : your Class containing the public static void main(String args)



Export destination : Target place



Library Handling:



Package required libraries into generated JAR



FINISH

Doing a (project->clean) and creating a new run configuration (with correct project and class name with main() method, selected) solved the problem for me.You just have to select the new run configuration while exporting runnable jar :)

When you click this option in Eclipse you should get a popup that lets you choose what files to export, you need to select the src folder.

I was having this same problem, and I was able to resolve it. Maybe you should cross verify the main class, that you selected in this project. It is possible that some other project's main class may have the same name as the main class you selected. Make sure the main class you selected is the one from the project that you selected.

The problem is your package. You probably renamed it, and in the export option, the program was confused, and it was using the first name of your package.

This is basically happen when you change package name under which you made your program. This will create confusion regarding package, as per program export, main method still written in old package.
To resolve it, Just copy it and paste it in same package with different name and then try to export it. Check for log too.

I was in the same situation. For me deleting existing eclipse installation(not not the project workspace) and opening the existing eclipse workspace with new installation of eclipse was the only thing that worked.

I continued to get the "no resources selected" error. I then did the procedure I am quoting and it gave me a MANIFEST file. Then I was able to create an executable JAR.

Quoting: "I exported the project as an archive file. Then I opened up a new workspace and imported the the archived project. After that I tried to export the project as a runnable jar, after two tries the jar runs as is it should."