> Can I ask why it is necessary for you to compile Turbine, Velocity and > Jetspeed as part of your own project
It is not .necessary., really. We've just found it useful to have third party code that we rely on in compiled form to make it easier to track down bugs within it. It also allows us to make changes to the third party code very quickly if we absolutely have to. Once you blow a deadline because you were using .jars and at the last second found you had to compile a third party library to make one little change, you never trust .jars ever again. > It seems a very complicated way of going about things... unless you > REALLY depend on code that gets added to those projects on a > day to day basis, which seems quite unlikely. No, we use stable, tagged code bases. Note that the third party code tends to only be compiled once. The point is to have it there if we need it at a moment's notice, not to rebuild with the latest and greatest at all times. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
