RE: maven with eclipse, mevenide et al
You can just run a goal to generate the .classpath and add the maven repo... http://maven.apache.org/reference/plugins/eclipse/goals.html -Original Message- From: Kenneth Simpson [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 27, 2004 2:24 AM To: [EMAIL PROTECTED] Subject: Re: maven with eclipse, mevenide et al 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. Hmm, that's news to me. I have 6 independent source directories in one project in Eclipse. Try going into the Properties for the project, click on the Java Build Path and add the source directories under Source. Also, there should be some maven goals for Eclipse to help set both classpath and maven repository path. - 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]
Re: maven with eclipse, mevenide et al
The issue isn't the number of source directories, it's the location. product-ejb has in the project.xml sourceDir../product/source/src/sourceDir This isn't allowed in eclipse. I could set it to an absolute path, but that's nasty as it assumes everyone checks out in the same location. On Tue, 26 Oct 2004 17:24:15 -0700, Kenneth Simpson [EMAIL PROTECTED] wrote: 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. Hmm, that's news to me. I have 6 independent source directories in one project in Eclipse. Try going into the Properties for the project, click on the Java Build Path and add the source directories under Source. Also, there should be some maven goals for Eclipse to help set both classpath and maven repository path. - 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]
Re: maven with eclipse, mevenide et al
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]
Re: maven with eclipse, mevenide et al
Yes, I'm thinking that the current structure probably needs to be modularised in a more intelligent way. It's not that maven is unhappy, it's more the eclipse problem of the sourcecode being 'elsewhere'. we used to have 1 project controlled by ant that build a heap of artefacts, such as client jar and ejb jar. So I effectively created 2 maven projects that did one thing each, and just said 'my sourcecode is actually in ..\common\src'. I guess I should get the common project (or project*s*) to do the compilation, and then do some kind of jar-ing or UberJaring to build my artefacts. On Tue, 26 Oct 2004 11:33:51 +0200, Eric Pugh [EMAIL PROTECTED] wrote: Take a look at the updated (in CVS) docs. I added a bit about using the generated source directory to import your xdcolet directory as a source directory. That way, when eclipse does a clean compile, it doesn't wipe out your source... I htink you are using xdoclet to generate a lot of the ejb stuff right? This works perfect for that... As far as how you are reading in the common code, shouldn't that be a seperate jar (and therefore project) that you are referring to? Maven doesn't really like to read in source from one place into multiple jars... Eric -Original Message- From: Nigel Magnay [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 26, 2004 11:01 AM To: [EMAIL PROTECTED] Subject: maven with eclipse, mevenide et al 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]
Re: maven with eclipse, mevenide et al
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. Hmm, that's news to me. I have 6 independent source directories in one project in Eclipse. Try going into the Properties for the project, click on the Java Build Path and add the source directories under Source. Also, there should be some maven goals for Eclipse to help set both classpath and maven repository path. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
