We are using the following layout:
projectRoot
|---applications
| |---application.j2ee
| |---maven.xml
| |---project.xml [...]
|---containers
| |---application.jboss (Self contained JBoss test environment)
| |---maven.xml
| |---project.xml [...]
|---modules
| |---application.domain (Hibernate)
| | |---maven.xml
| | |---project.xml [...]
| |---application.service (EJBs)
| | |---maven.xml
| | |---project.xml [...]
| |---application.web (Web layer, right now Tapestry based)
| |---maven.xml
| |---project.xml [...]
|---project (Here you put the top project xml everybody else extends from)
|---maven.xml
|---project.xml [...]We use the Eclipse plugin to generate the Eclipse projects (we have one Eclipse project for each maven project), and using this layout we're able to import all the projects in Eclipse using the Multiproject Import tool at http://eclipse-tools.sourceforge.net/. You may also use the Mevenide Eclipse plugin, but I have found several problems while using it, maybe you're luckier.
Of course thanks a lot to all the people in the list, and specially Vincent Massol for guiding me while I was struggling with the same issue :o)
HTH, best regards Jose
Nigel Magnay wrote:
Hi people. We've been using maven for a while now, with cruisecontrol, very nicely indeed, for builds.
Some of us use maven to do our local box builds, but more don't than do, and a part of that is probably our heavy additction to Eclipse.
Now, I've been using the IDE integration stuff, but I have a question (actually a 'how are you guys doing this). I've tried googling for this but I can't get search terms that provide a good answer :-)
We have somee projects that produce EJBs. So, in essence, we have 3 projects:
product-ejb : EJB Jar
product-ejb/target/classes product-ejb/target/xdoclet
product-ejb/target - ejb artefact appears here
product-client: Client Jar product-client/target/classes product-client/target/xdoclet product-client/target - ejb client jar appears here
product-root: Common product-root/src : effectively all the source code
Where product-ejb and product-client set their source dir to be '../product-root/src'. This is nice because our legacy ant scripts (that some people still live & breathe) just live entirely in product-root.
This all works fine for maven builds, but of course eclipse doesn't like its source files to be anywhere other than a direct descendent of the project directory.
I suspect this layout is a bit wasteful - for one thing, xdoclet and the compiler get run twice, but I'm not sure the best route to go. symlinks for the src directories occur to me, but that scares me both because we're NT, and that it may confuse our source control (and our developers....)
How are other people doing this?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
