In preparation to the first alpha release I have changed the directory
layout close to the de-facto standard of Java projects.
Why? => It makes the build process with gradle (and other tools) much
easier and requires less complicated build scripts.
Could some other developer please confirm that is possible to pull and
compile/run without error?
As the project file of eclipse is saved it should still work, but I
would like to be sure before I proceed.
Thanks,
Stefan
Included changes:
/src/main/java for all java classes required for running Rails
/src/main/resources for all other files required for running Rails (e.g.
images, tiles, xml-files)
/src/test/java for all java classes for testing Rails
/src/test/resources for all other files required for testing Rails (e.g.
test game save files and reports)
/libs/main for all external libraries required for running rails
/libs/test for all external libraries required for testing rails
I also changed the package prefix from /rails/... to /net/sf/rails/...
to indicate that the Rails namespace is derived from rails.sf.net
(sf = abbreviation for sourceforge).
This is also mapped into the directory structure of the Rails project.
There is one omission to this: The action package is still named
rails/game/action as otherwise the deserialization fails.
Unfortunately the workaround from
http://stackoverflow.com/questions/5305473/how-to-deal-with-a-java-serialized-object-whose-package-changed
does not work as intended if combined with the getFields() method of the
ObjectStreamClass which we use to support old Rails 1.x classes.
My intention is to replace the current serialization process of Rails
with one based on xml-files. I intend to use the simple library for this
reason (see http://simple.sourceforge.net/ ) as it is both easy to use
and adjustable and will allow renaming the action package to its full name.
|
