I think you may be able to do it if you put the parent and child projects at
the same level in the filesystem; don't nest the child modules in the parent's
directory. Thus, your parent pom will have
<module>../myappone</module>
<module>../myapptwo</module>
And the child poms will have something like
<parent>
<artifactId>parentArtifactId</artifactId>
<groupId>myGroupId</groupId>
<version>whatever</version>
<relativePath>../parent/pom.xml</relativePath>
</parent>
Get that to work outside of eclipse, then start over with eclipse and import
each one separately.
Jaikiran wrote:
Kent Narling wrote:
If you want to do this, why not use one of the maven eclipse plugins?
At least I know m2eclipse supports this very nicely...
The only reason i stay away from adding plugins (any plugins) to eclipse is
because
1) It makes Eclipse slow
2) The plugins sometimes start off uncontrollable actions (ex: downloading
dependencies etc...)
But if that's the only way to do this, then maybe, i'll have to rethink.
Isn't this supported from mvn plugins instead?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
