Thanx for such quick replies! In Q4E the only thing I see in the prefeneces pages is the ability to configure src/java-doc downloads as well as archetype url stuff. I need the ability to point it to a team-shared settings.xml or at least unconstrained ability to configure all of the options that would be present in settings.xml. I'll try looking for a later version as maybe this is a recent addition? I did install Q4E about a month or two ago. One other issue is with propsed flat-dir structure. Does the release plugin still have issues with flat structure? Has that been resolved? I'm really looking for an approach that won't leave me stuck again in about another month when we start cutting releases. Has anyone worked on a multi-module project with Eclipse and cut releases successfully? If so can you explain the best approach? There are a number of issues here that are worrying me.
Carlos Sanchez-4 wrote: > > Eclipse is quite limited for multiprojects > http://code.google.com/p/q4e/wiki/ImportingMultiprojects > > In Q4E you can configure the settings.xml in the Preferences. There's > no need to point to an external maven installation as it is already > included in the plugin > > On Feb 12, 2008 7:02 AM, Clifton <[EMAIL PROTECTED]> wrote: >> >> Hello all, >> >> I am a devoted IntelliJ Idea user with Eclipse experience trying to get >> my >> team acclimated with Maven. I'm having trouble sharing a multi-module >> Maven >> project with my Eclipse brethren through Subversion. In Idea I can merely >> check out the project root folder and everything just works. However I've >> noticed several issues in Eclipse all regarding the m2eclipse plugin. >> When I >> check out the project using either Subclipse or Subversive I get the >> option >> to check out as a Maven2 project. Checking out from root does not bring >> in >> the child projects as Maven2 enabled projects. If I checkout the projects >> individually the m2Eclipse plugin then proceeds to define a new pom for >> the >> project upon checking out. This completely hoses the build path and gets >> everybody confused as they have to manually redefine the pom and restore >> the >> dependencies. I've tried several attempts at checking out the project, >> all >> with no success. I've even tried the Q4E plug in which doesn't seem to >> allow >> me to configure an external Maven install or custom settings xml. What is >> the best practice for using Eclipse with a multi-module project? >> -- >> View this message in context: >> http://www.nabble.com/Maven2Eclipse-with-multi-module-projects--tp15434261s177p15434261.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > > -- > I could give you my word as a Spaniard. > No good. I've known too many Spaniards. > -- The Princess Bride > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Maven2Eclipse-with-multi-module-projects--tp15434261s177p15438835.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
