> -----Original Message----- > From: Richard Bair [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 14, 2004 7:50 PM > To: Maven Users List > Subject: Re: Reactor & SubProject interdepencies > > [aside] > Well, I was going to use multiproject, but honestly I > can't figure out what is the "best practices" way of > doing things, and what isn't. From a noobs > perspective, Maven looks really powerful but I have > almost *no* idea what the preferred way of doing > anything is. Aside from having to learn how to script > in jelly, what goes into > build.properties/project.properties/project.xml/maven.xml > or what some obscure error means (the current one is [..,] > [/aside] > > Thanks David > Rich Probably one of the reasons why such practices has not been yet clearly communicated and described is that some of those of practices were born with maven. In order to tell what good practice is or what is not you need to have a substantial experience. AFAIK no commonly used tool before maven has a support for such features like "project inheritance" and "reactor" hence nobody had real experience with them. We are still experimenting with those features, learning from our users' experience and trying to find best ways of doing things. There is a new concept coming to maven - Unified Source Directory, which will be our proposition how to structure projects in the way which will allow to have things quickly and smoothly done. It is still a work in progress, but once it's done it will be really helpful as it will be clear "how the things should be done".
At the moment you may look at more complex projects like Apache Geronimo to learn how they organize their build system. We are doing the same :) ... to learn what kind of functionality people really need from maven and what is working for them and what is not. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
