On 10/23/05, Vincent Massol <[EMAIL PROTECTED]> wrote: > > 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) > > Ok. I would hate to have to change my preferred build directory structure > because an IDE cannot cope with it. The projects I'm referring to here are > open source projects and people should be free to use whatever IDE they want > to work on the project. Telling them I'm using a sub-optimal directory > structure because I use Eclipse and the m2 eclipse plugin wouldn't be a good > reason enough IMO :-)
Absolutely true, but using a single project VS multiple modules is a lot more than a different directory structure... Spring for example uses a single project (not with maven) and then split the jars during a custom and build: it's a lot simpler to handle but you end up with an eclipse classpath with tons of dependencies, and that's not always recommended (maybe you will introduce dependencies in packages where they are not expected). BTW, if you want to try working with a single eclipse project that should be anyway supported if you install WTP (there should an option about "allow multiple modules in flexible projects" somewhere). I just never liked it because of this classpath limitations... Oh, and if you are going to work with j2ee projects you can also have different kinds of projects (jars, ejbs, wars, ...). Using a single module per project is IMHO a lot better in this situation, I don't think you want to mix everything... > > > 2/ How do I share eclipse settings between projects? See > > > http://jira.codehaus.org/browse/MNG-1062 > How do you share the default code formatter with other person working on > your project. Do you export something, check it in in your project and ask > developers to import it in their project? That wouldn't work in an open > source environment as you can't consider that developer's workspaces are > going to be used only for developing on your project... Yes, at the moment that's left to the developer, I usually export the code formatter configuration and publish it on the website. Unfortunately adding this kind of settings automatically using maven is not so simple... I will see if I can add something to the m1/m2 eclipse plugin... > Thanks Fabrizio for this feedback! That helps me to understand the pros and > cons of each approach :-) You are welcome, you are talking to another maven/eclipse user trying to get the best of both ;) another suggestion: if you are starting from a maven project with a parent project in the root dir, try creating a new project in eclipse, calling it (yourproject)-parent and linking all the needed resources (pom.xml, the /src dir, ...). In this way you will be able to use resources from the root dir in eclipse without having to change the project structure at all. fabrizio --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
