RE: Barracuda: Build system modifications

Hi Christian,

I'll forgo comments on the other stuff.  We'll have to agree to 
disagree.  I'm actually rather interested in seeing your proposed build 
structure at work now that you've talked it up :-)

It certainly does make it simpler to not change the build around so 
much.  Does this cause problems for you though?  It seemed that you wanted 
to modify things in Barracuda to better match up with how you do things in 
your proprietary projects.  I have no such requirement.  I just wanted a 
build I was comfortable with.  Like I said before, I actually defer this to 
you because I really don't have much time this weekend or next week to make 
any changes and I'd like to get the server to hosting just as badly as 
everyone else.  I don't want to hold things up.

If the changes you propose below are truly what you want, then I'm ok with 
them.  Since it doesn't change things much, there will probably be less 
chance for things to go wrong.  As far as the contrib goes, I'm going to 
miss how I got things working.  I thought that was pretty slick how I did 
it, even if it needs some explanation.  Moving all contrib to another 
module is probably the best thing.  It would still be good to be able to 
have one build file that can control all the contrib projects similar to 
how build-contrib.xml does now...except build-contrilb.xml would now be the 
main build file whereas it only acted as a helper to Barracuda's main build 
in the current setup.

The main goal is to get things up and running.  I have a couple mods to 
commit and need to commit Stefan Ambruster's contrib project that he sent 
to me a couple weeks ago.  It will be good to get this transition over with 
and get on with coding.

Again, if you really feel like doing less than you originally proposed, 
that's fine.  But, at this point, I have no issue with your proposed build 
process.  If you are familiar with it and can get things up and running, 
I'm sure it will be just fine.  Since I don't have the time to contribute 
to writing the new build, that will have to be something I leave to you 
(and others) for now.

Go ahead and pull out the contrib stuff.  Right now they have some 
dependencies on the main Barracuda build and some properties files in the 
Barracuda build.  That will have to be remedied later when I get a chance 
to manipulate them.   I will still have commit access to the contrib 
projects, right?  I have don't most of the committing since Diez originally 
put his project up, so that would make sense.

So, do whatever you need to do to get all this up and running ASAP.

later,

Jake

At 05:56 PM 1/3/2003 -0700, you wrote:
>Ok, so in light of all this discussion, I think we can safely conclude that
>there are lots of different ways of doing builds and that many of us are
>going to have significantly different opinions on how best to go about it.
>So...here's what I'd like to propose:
>
>a) I think we should leave the Barracuda tree as it currently is (not moving
>the src trees from the top level under WEB-INF); I think we do still need to
>move the cvs jars into a lib-cvs, but that is a very minor change.
>
>b) I think we should consider moving all the contrib projects out into their
>own cvs modules. This means that our cvs module structure would look
>something like this:
>
>/Barracuda
>/BarracudaDiscRack
>/Contrib
>     /dbroggisch
>     /christianc
>     etc.
>
>This would then make it really easy for contrib packages to use whatever
>build structure they want, and would also keep the master source tree much
>simpler. Plus, it's still relatively easy for Shawn to administer in terms
>of permissions.
>
>SO...what do you think? Jake? Shawn? Anyone?