---- Original message ---- >Date: Wed, 04 Jun 2003 11:31:45 +0200 >I see this problem from a bit different perspective. Most, if not any >single project - multiple jars concerns can be solved by structuring the >codebase corectly.
"Correctly" -- a 30 person project with multiple teams, thousands of lines of code and several 3rd party dependencies doesn't map to the simple "correctness" of, e.g., jakarta-commons-lang. Ya gotta think bigger, more complicated, and add a few professional managers to understand my situation. >It's not that maven is really lacking anything, it just encourages >different approach to codebase management that is currently used by >many projects. I would say "enforces" rather than "encourages." Maven is lacking support for multiple codebases and outputs per project. Believe me, I would love to organize our whole project like Jakarta Commons, but things are a lot more complicated in medium to large commercial software projects. But obviously a tool designed to build tip revisions of Jakarta Commons out of CVS is going to have to stretch to accomodate larger and more "sophisticated" (or 'incorrect') project structures. >I'm aware that restructuring may be not a feasible option >for many of them, so Maven provides support for 'incorrect' codebase >sturcturing to some extent. You should reconsider your use of "correct" and "incorrect"; it sort of discounts smart people who are more concerned about whether the tool is reasonably flexible than whether they meet your notion of "correct" project management. >Over time this support may be further >improved, but this is not a high priority goal. It should be. I think things will get better -- if more people start to use Maven and contribute back to it, everything should improve. I am willing to help. Scott Stirling Framingham, MA --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
