Hi Mehmet,
Welcome to this forum.
Originally posted by Mehmet Atlihan:
Although it is not clear according to the specifications I have , I dont think it is a good idea to enforce the grader to edit his classpath enviroment variable manually isnt it?
You are absolutely right, it is in fact a very bad idea to force the grader to edit his classpath environment variable manually. I suspect the grader might think it is such a bad idea that he might automatically fail your project.
The good news is that this is relatively easy to fix. One of the main purposes of using an executable jar file is that it frees the user from classpath concerns. I'm assuming you used packages in your development. Let's say you have three packages: suncertify.db, suncertify.rmi, and suncertify.client. Let's further assume that all your *.class files are in a classes directory. The contents of that classes directory should look like this:
where
+ name is a directory.
Then, the following command should create a runme.jar:
The runme.jar should then be runnable on any computer that can support a JVM. That is, anywhere you can do "java -version"
you should be able to do "java -jar runme.jar alone". It should not matter how the classpath is set since you will not be referencing it.
Regards, George
SCJP, SCJD, SCWCD, SCBCD