Thanks everyone for the inputs. Let me give the Eclipse plugin a try :)
Eugene Kuleshov wrote:
>
> Rusty,
>
> The startup issue been fixed while ago. The project import and updating
> dependencies may take some time for large project, but nothing like that
> is happening at Eclipse startup a
Rusty,
The startup issue been fixed while ago. The project import and updating
dependencies may take some time for large project, but nothing like that is
happening at Eclipse startup anymore.
regards,
Eugene
Rusty Wright-2 wrote:
>
> I forgot to add, I agree with Kent; using the m2ecl
I forgot to add, I agree with Kent; using the m2eclipse plugin really makes it
much nicer; it keeps your classpath up to date and all kinds of other nice
stuff. Just learn to get in the habit of sitting back and waiting for it to
finish doing its stuff when you start eclipse; for me the price
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
../myappone
../myapptwo
And the child poms will have something like
parentAr
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
If you want to do this, why not use one of the maven eclipse plugins?
At least I know m2eclipse supports this very nicely...
2009/1/23 Jaikiran
>
> I have a multiple module project with this parent pom containing this:
>
> myappone
> myapptwo
>
>
> The myappone and myapptwo have their own poms a
I have a multiple module project with this parent pom containing this:
myappone
myapptwo
The myappone and myapptwo have their own poms and are jar artifacts. From
the top level parent i do a
mvn eclipse:clean eclipse:eclipse
And then from Eclipse (which does not have any plugins) i do a Fil
