Ralph Goers said: > > Having said all that, I'm not sure why a Jetspeed customer really needs > to know about any build tool. I should be able to download a war or ear > file, install it into my container (perhaps with a configuration script) > and run it. I really should only be concerned about the build tool if I > want to modify Jetspeed source. >
WOW. There sure are a LOT of assumptions in that paragraph. Have you worked with many portal projects in an enterprise environment for very long? If so then you should probably know that more times than not, you end up customizing big pieces of the code in order to integrate with pre-existing infrastructure ... not necessarily by choice. How many projects in the history of software development have accomplished 100% of what everyone wanted, 100% of the time? I'll tell you the answer is ZERO. So yes, people need to modify the source. By nature, open source projects are ... guess what ... OPEN!?! Meaning users (customers as you put it) can and should be concerned about the build tool if they need or want to modify the source. > If you buy into maven's way of doing things then you only have to write > "build logic" for things that are unique to your project. With ant you > have to write everything. Once again, this assumes that the developers have thought of everything and will designate the "pockets of code" that can be customized. Then when this turns out not to be the case (99% of the time), anyone wanting to customize the source has to learn the complexities of these monstrous NESTED maven scripts. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
