Without knowing details all I can give are general suggestions... - Things you want to version/branch as a unit go in the same project (may have several modules). - Common things that are used in more than one project go in a separate project (may have several modules) and are depended on as needed.
-Dave On Tue, Mar 2, 2010 at 11:24 AM, user09772 <sonnyh...@gmail.com> wrote: > > I've used maven in very simple projects. > > Currently I'm in the process of developing a somewhat larger application. > I'd like some ideas from experienced users on how i can layout the following > situation. I have split a project into various high level maven projects. > > some projects are rest service > some projects are chains (commons) > some projects are commands for use in the chains > > There are other pieces which are not as important. The rest services > projects acts like the parent which will include a mix of other projects as > necessary. I'm curious how one would layout a project like this? Any > tutorials will be helpful on this type of setup (preferably using m2eclipse) > . Thanks. > -- > View this message in context: > http://old.nabble.com/Newbie-Maven-layout-question-tp27759332p27759332.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
