I have created a Repository for MapTool on GitHub which can be found at https://github.com/RPTools/maptool
The build script has been created from scratch making the whole thing -- at least I think -- easier to build.
I will be accepting contributions against the version in GitHub. If you want to make contributions and you don't think it will
just be a one off the easiest way to do so is create a Github account (its free) and them fork the above repository which will
create a copy in your account. Once you have made what ever changes you wan't to you can issue a pull request which will
let us know that you have code you would like merged (and provide any details as well) that is easier to merge than keeping track
of in some ones email box. The other advantage of forking the project is it allows anyone to see changes that people are making
(as long as they are committed to the repository) hopefully leading to easier co-operation all around.
The build now used gradle instead of ant this helps manage dependancies easier and keeps the produced binaries out of source
control. The build-resources/README.md contains instructions on how to build the thing. The other projects that MapTool depends
on such as parser, rplib, dicelib etc are not yet on GitHub, I will be migrating those as needed (so let me know if you need them
in there before I get around to it). The build uses gradle wrapper so there is no need to install gradle to build MapTool, because
of this the first time you build the source it will take quite a while as it needs to download gradle components, then it will download
MapTool external dependencies. This will be cached so subsequent builds will be significantly faster.
All major IDEs support git, and most support GitHub specifically if you want to use an editor that for some reason doesn't support
it git (or you don't like its support) for some reason there GitHub supplies its own GUI tool for Wndows and Mac OS X or you can use
the usual git command line tools. There are no editor projects/configurations checked into source control as they shouldn't be
needed as most IDEs should be able to pick up all dependancies from the gradle build file, if you are using an editor that can't
let me know (I am sure eclipse will have problems but mostly because it always has problems with everything).
Only small steps so far but at least there are some steps happeing :\, speaking of small steps the rest of this week is kinda busy
for me so don't get discouraged if I don't get a chance to look at your contributions until late in the week or early next week. I
will monitor this thread and answer any questions though, and if need be try provide more detailed instruction based on feedback.
But in the mean time here are some links to hopefully help you on your wayFork a RepositoryFlow used by GitHubGitHub GuidesPro Git (open source book)GitHub YouTube Channel with training videosGitHub Learning Resources