From what I recall, the only thing that needs to be "fixed" when you build a local copy is the build.number file right? I assume nothing is uploaded anywhere correct?
Yes, that's correct. If I do any commits to SVN it will pick up the build.number change and add that to SVN but that's not a huge deal. I also typically turn off the autobuild in Eclipse and clean the project so that there is not a version.txt
in the bin/
directory in my maptool project hierarchy.
So, how about you do the build, make it available in a limited membership forum for the testers to check out for a few days and if it's good, move to the correct places for the zip and jnlp files. If problems that have to be fixed come up, just svn revert the build.number file, apply patches and redo.
Is that something that is possible with your current build process?
Sounds fine to me. The Java Developers group on the forum is an optional group that users can add themselves to; I could put the files in the General > Developer Notes > Java Programming Info forum where those people who are in the Java Developer group would see it. Does that work for you?
Would you want to see a ZIP file identical to the current build setup or just the maptool/rplib/parser JAR files? If we go with full files I would likely turn on attachment pruning for that forum so that old attachments that are 18MB+ are eventually deleted...
Otherwise, I could create a new group and make you the group administrator. Group membership would be "by request" and you would need to approve those requests, then that group could have access to a separate subforum under General > Developer Notes (or somewhere else that you think is appropriate).