Hey guys I'm having a tough time with this one and have been unable to find much through Googling and researching, so I thought I would just ask you guys. I've been using NetBeans to develop my games in (using Slick2D) and I'm trying to switch over to JDeveloper (because that's the IDE we use at work) and I can't seem to get even a test game up and running.

I have no problems setting up the Slick library and linking the classpath to it (in Project Properties). I am even able to set the runtime Java Options to (in my case) -Djava.library.path="C:\Program Files (x86)\Java\slick", just like it is in my NetBeans projects. However, every time I try to run an application (Slick application that is, regular ones work just fine) I get a windowed error message that says "Could not find the main class: Files. Program will exit" with "Java Virtual Machine Launcher" as the window's title.

I'm thinking that it has something to do with an incorrectly typed path somewhere (the idea being that the "Files" from the error is part of the \Program Files (x86)\Java path, but I've checked all my paths in the project properties that have "Files" in it and they all are fine.

Has anyone else tried using JDev with Slick2D and been successful and if so, do you have any ideas on how to fix my problem?

Thanks guys.

Well that's the kicker, I don't have any classes named "Files" and my main class is called "Game". That and the fact that the error window that pops up is titled "Java Virtual Machine Launcher" makes me think it is something in my JVM Options (Located under Project Properties > Run/Debug/Profile).

And as far as the -Djava.library.path stuff goes, I was told to do that from the Documentation on the coke and code site (for NetBeans) and so that's why I was using it for JDev, because I figured that type of thing would be the same across the different IDE's.

I bet the "Files" is from the Program Files specification.  Try the usual quoting, escaping, etc.

I'm pretty sure it's in that -Djava.library.path also, but I'm a little slow today, what do you mean by the "usual quoting, escaping, etc."?

Sometimes referencing paths that have whitespace in them are causing problems. You should refer the classpath to a relative destination instead. That way you will also have an easier time when desploying, because it can be ran with the whole installation inside a folder, instead of spreading it out throughout the computer
Try doing something like "lib/" and keep your libraries and native stuff in there.

Glad to help.