On 2/2/06, Geoff Longman <[EMAIL PROTECTED]> wrote: > Downside. you have to put the child projects in the parent folder. > Which means you can't check out the parent and have the children in > eclipse without importing them. > > You can check out the children individually directly into eclipse as > long as you have already run a maven install on the parent. > > Not perfect but not bad.
Yes, that's the way maven2 eclipse plugin works , and that's is terrible by my point of view. You end up having a directory per module in your workspace plus a dir for the whole process (maybe just to handle docs, scripts, deploy time config etc) and for the SCM they're all different working copies so if you put hands here and there you have to update the others, i find it at least boring and error prone. I probably could take it as a good practice for a really big dev team which as strict separation of concern between developers. But as you I've used maven2 just for a short time (a month or so) and could see some benefits, so I'll wait to see where it ends. -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
