Difficulty being, it's not in any of the traditional places.
The first line of game.java is "package mycompany;"
I have created a jar containing all the classes of mycompany in "Game.version.jar".
The jar's manifest includes the line "Main-Class: mycompany.game", and is followed by two blank lines.
The jar includes game.class.
What am I missing? I'm not sure whether it's an improperly-constructed .jar, a naming problem, a classpath problem, or something completely different.
I'll keep reading up on executable .jars, but if you have a thought in the meantime I'd love to read it.
Be aware, too, that case is significant in class names. You appear to be all right -- you say the class is game, and the error message is looking for game; I mention it partially because class names are traditionally camel-cased, and so this class would normally be spelled "Game". If it were, then the manifest would have to have the G in upper case as well.
As long as you're consistent across the board, this should still work, though you will find that other java libraries/packages/programmers will mostly use camel-case for classes.
Joined: Oct 14, 2005
Blast! J. Neal identified it correctly, I forgot about directory structure. I now have an executable .jar.
... now to hunt down the other bugs floating around...