changing java classpath for jar files on mac

Changing Java Classpath For Jar Files On Registration Can Be
Changing Java Classpath For Jar Files On Mac Store And
Changing Java Classpath For Jar Files On How To Do Certain

Changing Java Classpath For Jar Files On How To Do Certain

Were not going to explain how to do certain things, because the article would be too long.

There is little information and very few tools to do it; in fact, only one tool available to pack a jar file into an app.

This was a mandatory step to publish our game inside and outside OSX App Store.

User can disable Gatekeeper, but we consider thats fair to demonstrate youre a valid partner of Apple and you app is trustworthy.

Changing Java Classpath For Jar Files On Mac Store And

This is an essential requirement to publish in the Mac Store and it has a different signature than Gatekeeper.

It doesnt have to be Oracles Java Virtual Machine, but its the one we used.

We need Java 7 (in our OSX system, we find only Java 6 as preinstalled).

Once we install our JVM with Java 7, we must go to one of the jdk or jre installations.

For instance: homeLibraryJavaJavaVirtualMachinesjdk1.7.051.jdk.

We click on the icon, and if the active version of Java is SE6 we have to disable it, and check SE7.

We create a folder with all necessary thing to build our app (I called mine build).

For instance, if my build folder is at the Desktop, in the Terminal I must go using.

In classpath we type the directory where the AppBundler is located.

Changing Java Classpath For Jar Files On Registration Can Be

This registration can be done afterwards, and its only necessary if youre going to distribute in the Mac Store, not for third parties.

In our case, we used Eclipse and we did spend so much time setting the main class of the app, while this IDE actually used his own Leader class when creating the exe jar.

This entry is optional and if we dont include it in our app it wont have an embedded jdk.

Good news are that doesnt require much space; bad news are that if the user doesnt have the correct jdk or jre, the app wont run, so its poorly advisable.

This includes the path where our jdk is located; if we dont know it and were using Eclipse, we can go to Preferences and check the jre.

To sign an app and be accepted by this technology we must create a certificate with a Team Agent account.

Be very careful with this: to publish outside the App Store you must create a Developer ID Application Certificate or Developer ID Installer Certificate, depending on whether we want to only sign the app as it is or to pack it into an installer (that also has to be signed).

Once created and added to the Keychain (check carefully we have the private key associated to the public one), we just set into the app directory and type.

Our core values are building original gameplays and try to bring to the game design process modern things like social and new interaction models.