On 10/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > I have been a long fan of using a master eclipse project. I'm now trying to > use the m1/m2-preferred strategy, which is to have one eclipse project per > module. I'm doing this using "m2 eclipse:eclipse".
well, actually that's also the eclipse preferred strategy. Multiple-modules-per-project support has been introduced in WTP but it didn't enconter a good feedback from users. And anyway, this will force you to have a single common classpath, which is probably not desiderable if you are using multiple maven modules... > 1/ How do I edit files that in pom packaging projects (i.e. top level > directories)? This is for example where the common pom.xml files are > located. normally I move the parent project to a subdirectory or, if the parent project only contains a pom.xml file, I import it in another project as a linked resource (calling it pom-parent.xml or something similar) > 2/ How do I share eclipse settings between projects? See > http://jira.codehaus.org/browse/MNG-1062 For large workspaces I usually add modules related to the same project (for example all the maven 1 or maven 2 modules) and set up a default code formatter in general preferences. For project with a limited number of modules at the moment I generally choose the code formatter setting manually after running eclipse:eclipse (not optimal, I know, we could try to improve it...) fabrizio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
