On Fri, 2006-03-03 at 10:46 +0100, Mark Wielaard wrote: > Hi, > > On Thu, 2006-03-02 at 12:05 -0500, Thomas Fitzsimmons wrote: > > On Thu, 2006-03-02 at 00:06 -0500, James Damour wrote: > > > Lillian Angel has done a truely remarkable job squashing rendering > > > problems, so what once looked like [1] now looks like [2]. > > > [...] > > > There are still a few little bugs (which appear to depend on one's > > > operating environment:-( ). I'll be writing up Bugzilla reports over > > > the next few days/weeks to help run down the last few problems. > > > > Great, thanks. > > Yes thanks for your support! It looks like MegaMek is actually playable > now on our free stack. I look forward to it being bundled with the > different distributions. Although I am afraid what it will do to the > productivity of our hackers :)
I *may* inspire them to want to implement v1.5 APIs so that they can use all the cool new features in the development branch of MegaMek! :) > > > I also looked into the compatability between MegaMek clients and servers > > > running on proprietary and free VMs. There was an initial hiccup where > > > I was getting incompatable serialVersionUID, but I quickly realized that > > > the problem was caused by my compiling MegaMek twice, once with Sun > > > tools, and once with Free tools. When I gave both VMs the same set of > > > classes (or JAR file), they could connect without difficulty. > > > > Isn't this the point of serialVersionUID though? If someone builds and > > runs MegaMek with Sun's tools and another person builds and runs MegaMek > > with free tools, the two MegaMek instances should be able to serialize > > and unserialize each other's data. Where this isn't the case don't we > > need to update our serialVersionUID fields? > > Yes, and if we did our homework right then this is the case. See also > our hacking guide > http://www.gnu.org/software/classpath/docs/hacking.html#SEC19 I apologize for being unclear. The hiccup was indeed caused by MegaMek classes missing serialVersionUID fields. I have fixed this problem and submitted it to CVS. I have also added the files, .classpath and .project that Thomas Fitzsimmons sent me so that CVS checkouts withing Eclipse will automatically be built. I do not run Eclipse, so I can not directly confirm that these files work correctly, and I refer all problems with them to Thomas. -- James Damour (Suvarov454) <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
