Michael McCallum wrote:
Hmm, I was hoping that there would be an alternative. Take the scenario where I'm working on ModuleA and ModuleBMake each module into a maven project and release them to your local artifact repository... Then you can define the dependencies just like all the other projects.
(i.e. a single developer is contributing to both modules). Let's say ModuleA is a webapp and ModuleB is
some backend stuff. In order to test ModuleA I've have to deploy ModuleB - but if I'm developing
both modules at the same time I'll need to do a deploy of ModuleB to the Maven repository for
each change I make to it.
Do you think a developer should be able to work on two cvs modules (i.e. two maven projects) in
parallel without having to redeploy on each compile?
ct
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
