We create a separate Eclipse project for each subproject. Our daily build uses multiproject on the whole deal, although this appears to be complex to maintain. But it's much easier for a developer to deal with only one subproject at a time.
Each of the subprojects generates a jar that lives in a maven repository, and the maven and Eclipse classpaths point to this, so the subproject developers are pretty well insulated from each other. This approach seems to work pretty well. If multiproject were easier to use, I might try developing with the whole thing inside of Eclipse. Please send the list a description of how it went for you if you try that! --Chris -----Original Message----- From: Aaron Bell [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 13, 2005 5:24 AM To: [email protected] Subject: best practice with Eclipse? I am just getting started with Maven. Can anyone advise a practical way to use Eclipse on a Maven project with multiple subprojects? For example, are people using a separate Eclipse Java project for each subproject, or a single Java project for the whole hierarchy? The former is implied as the 'eclipse:eclipse' goal (run on the top level) generates .classpath and .project files for each subproject. If I use a single Eclipse project for the whole lot, I then have the problems of: a. merging the .classpath dependencies from each subproject into the top level .classpath b. managing *many* source locations in the Build Path Thanks - Aaron --------------------------------------------------------------------- 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]
