One Subproject = One Eclipse Project
\toplevel
\root\project,.xml
\subproject1\project.xml
\subproject2\project.xml
Etc.
Use extends to have all the subprojects inherit from the common root
project.xml run all the multiproject goals from.
With the new Eclipse 3.1M5+ you can do a bulk import of all the subprojects
and you can use multiproject:goal with -Dgoal=eclipse to generate the
.classpath and .project files.
It works pretty well
Jim Mochel
-----Original Message-----
From: Jamie Bisotti [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 13, 2005 9:33 AM
To: Maven Users List
Subject: Re: best practice with Eclipse?
I'm currently doing the latter...though I'd love to hear of a better way.
Jamie
On 4/13/05, Aaron Bell <[EMAIL PROTECTED]> wrote:
> 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]
>
>
--
Jamie Bisotti
Software Engineer
Lexmark International, Inc.
---------------------------------------------------------------------
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]
