Re: [Openrpg2 dev] First try at providing some help

[Snowdog <sn...@ga...>]

Mark Tarrabain wrote:
> Mykel Alvis wrote:
>> OK. I must be missing that somehow.  I don't have tests in the repo that 
>> I'm looking at, but  I did just locate the build scripts.  I was blind.
> The tests/ directory doesn't exist in the svn repository, but you can 
> make one yourself, as I did.   It wouldn't be a bad idea to have the 
> directory in the svn repository anyways with a few JUnit tests in it for 
> individual classes to give developers examples to follow.

The only reason the unit test directory doesn't exist in the SVN is that 
  I never wrote any tests (at least none that were legitimate 'unit 
tests') while coding the majority of the core code. If unit tests have 
since been created by all means post a patch file to the tracker and 
I'll push them into the SVN repository.

> 
>> I have no issue with netbeans.  I'm sure it's working well for 
>> everyone.  What I'm interested in is the "outside of the IDE" build 
>> that's the more generic case.  With ant, there's always a matter of 
>> integrating dependecies into the build and eventually that turns out to 
>> make the build script even more complex, which I generally think of as a 
>> bad thing.  Furthermore, in the case of Netbeans, it means that anyone 
>> who wants to actually work on the project has to do that within 
>> Netbeans, which I don't care for.
> 
> No, not at all.  The ant build files supplied with OpenRPG2 are made so 
> that any new files put into the source tree are automatically included 
> into the build in the appropriate package or directory inside the jar 
> file.   This means that the maintenance on the build file drops to 
> effectively zero as there is no need to handle more dependencies or 
> targets than what is already there.   A developer could actually use any 
> development environment they wanted, or even just a plain text editor. 
> It will not cause problems in any way for anyone else if their work is 
> added to the repository.

As Mark points out we are not using complex ant build files. The ant 
build scripts simply make the assumption that everything must be 
compiled. Which is usually not a problem after an initial full compile 
most of the compiled source stays static and doesn't need to be recompiled.

As for dependencies: its really amazing how useful javac error messages 
are, they do a wonderful job of letting you know you forgot something. 
;-) Seriously though the current ant scripts make sure the entire source 
tree is compiled properly during the build process.

--Snowdog