Since day 1, ASoD has been developed on NetBeans. Netbeans and ASoD have grown up together and passed through many releases together. But now, Netbeans is being completely stupid. And the Netbeans project people seem to DENY this even though there are many posts about this issue...
So basically, I can't release anything since Netbeans is making corrupt jar files without building them manually.
Whenever the jarfile is loaded, it spits out an error saying that the main class can't be found. Then it exits. But when you run it from the sources (pre-jar packaged) you get a completely functional program. So, until I can resolve this, nothing can be released.
I have examined the jar file's manifest, unable to find a problem:
Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.1 Created-By: 14.2-b01 (Sun Microsystems Inc.) Main-Class: amongSeasOfDust.GameRoot Class-Path: X-COMMENT: Main-Class will be added automatically by build
I tried renaming Main.java to GameRoot.java using re-factoring and that did not work. Then I tried selecting a different main class (all the forms such as the standings display have these) and none of them work.
So, I tried reinstalling Netbeans and creating a new project. This did not work either. Therefore, for not, the project is stuck on your side. I can still add new content but until a solution is found nothing will be published.
There is a HOW-TO up, its been up since the beginning, of how to get the bleeding edge source code from the SVN repository. If you really want to keep up you can download the source code and build it yourself with the IDE of your choice.
Option 2 involves me manually packing the JAR, which I would really prefer not to have to do. If I have to, I will. But I think I need to resolve why Netbeans randomly choked up here. No one in the forum posts I've read seems to know why this even happens, and no one I've seen has a working solution.
Have you seen this?
It is important for me to know if you have seen this error or ASoD otherwise did not run:
If you ran it from the command prompt, you may have simply seen a series of exceptions. If you used a shortcut to launch it, a command prompt randomly flashed on your screen.
If you have seen this error, please email me at email@example.com or post as a reply to this article. I want to find out how bad this is, because I may have released a corrupt jarfile as a release. I tested the jar before it went out but you never know...
Thanks for your Patience
ASoD, like all major software projects, has run into a massive issue. All projects hit these at some point, often times it is an issue where the idea is unfeasible or cannot be implemented as expected. Our issue seems to be JRE/Netbeans corrupting jarfiles.
ASoD has survived these issues before, the last big stall was when the source code randomly would not compile (throwing meaningless errors). It turned out netbeans had corrupted an XML file, I figured that out after 4 days of analyzing my code.
ASoD is a strong project and can hold up to these things, ASoD will not die anytime soon.