Kumar, Vaidhyanatha K. wrote: > The existing project looks like this > ProjectA -- project_a.war > mod1 --mod1.jar > src/java > web > mod2 -- mod2.jar > src/java > web > mod3 > ....... > ..........
> To use maven & eclipse, Should be creating project & subprojects and > convert them to eclipse project ?? Since mod1, mod2 etc are > identical in the directory structure , I think it is a overkill to > create various subprojects. The source code mod1, mod2 etc are in > Clearcase. How do I move forward? Thanks for your help. True enough, there is a dilemma, and there is no obvious solution. The Eclipse way is to set up each module as a separate project, declare dependencies between them using Eclipse UI. This lets you use Eclipse for daily edit-copile cycle. The downside of this approach that you need fairly complicated custom Maven configuration for assembling your application and for generating reports on the whole codebase. The Maven way is to set up a single elicpse project with subdirectories for each module and use simple and standard reactored build. At the same time you will need a fairly complicated Eclipse build path setup to take advantage of the builtin incremental compiler, and other features. Note that in a reactored build you'll get separate reports for each module, unless you come up with a non-standard Maven configuration. R. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
