-warner
On Sunday, October 19, 2003, at 05:21 PM, [EMAIL PROTECTED] wrote:
Warner Onstine <[EMAIL PROTECTED]> wrote on 18/10/2003 08:13:01 AM:
On Friday, October 17, 2003, at 02:57 PM, Sonnek, Ryan wrote:
Here's what I've had to do: 1. make sure your project is not nested (ie: your parent project is parrellel to your children projects) 2. mount each module into eclipse as a separate project. 3. run maven multiproject:goal -Dgoal=eclipse to generate the .classpath and .project files.
What if my subproject relies on a core classset that is my "main" project? From what I'm seeing it doesn't generate that dependency for me.
Then you'd specify
<dependency> <!-- usual stuff ! ...... --> <artifactId>main</artifactId> <properties> <eclipse.dependency>true</eclipse.dependency> </properties> </dependency>
-- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
--------------------------------------------------------------------- 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]
