Jeff Martin wrote:
>
> about 6 months ago I added build support to Alexandria. It
> seemed to make sense that since I wanted to test build and
> Alexandria already had a means getting hold of the source
> from cvs without to much hassle it seemed good to just added
> in the ability to kick off a build.xml file is there was
> one.
And I was unaware of this when I started Gump. Whether I would have done
anything differently, I can't tell you, but I will say that I haven't spent
as much time as I should trying to help out integrating the code. I will
also say that the Gump code itself is also not where my focus us.
> This mean where I work we have a hourly process that checks
> out all the code and builds it (also runs JUnit tests) and
> produces a nice html page with shows any build errors in
> red. This works pretty well, what it doesn't provide is
> confirmation that any interproject dependencies are not
> being broken buy code which is in development, this is
> important information for some people but distracting for
> others who what information on how their changes are
> affecting their code not how other peoples affect their code.
My personal feeling is that the cvs boundaries are artificial. Being told
about person x's change which breaks my code, but not person y's because
the two changes were checked into different cvs trees doesn't make sense to
me.
> The other side of this is to look at the differing ways in
> which the actual build is handled. Alexandria used to be
> based around bash, but it became clear that Using Ant
> throughout the process was a better way to handle things.
> I personally would like to see Gump go the same way, but
> I don't want to through out the baby with the bath water
> so we're not just going to abandon Gump as it stands at
> the moment.
For the record, what I care about most is the content of the project files.
That's certainly where I spend most of my time. I'm not talking about the
specific tags - but the logical interrelationships and concepts expressed
within it.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
