you can right click on one of the project root folders, select the maven
item and one of the sub-menu items will do what you want
-S
On 17 June 2010 12:28, Daniele Dellafiore wrote:
> M2Eclipse does some things fine but not all.
>
> Use case:
>
> pom A define a resource folder
> I have in eclip
M2Eclipse does some things fine but not all.
Use case:
pom A define a resource folder
I have in eclipse, imported with M2E, project A and B, the latter inherit
from A.
Change the resource folder in A from eclipse, save.
Nothing change in eclipse.
So while changing a dep in the pom make the buil
> Actually, m-e-p does not create any .project while M2Eclipse import both of
> them... and the multi-module is useless and I will just delete it.
IMO you are better off just switching over to m2eclipse full time
instead of continuing to fight with m-e-p.
Wayne
--
Mixed feeling for me.
MultiModule pom project aren't to be imported as a project, I do agree.
But parent kind of pom project, I would like to see them imported. Problem
is that there is no way in maven to make a distinction.
Actually, m-e-p does not create any .project while M2Eclipse import both
On Tue, Jun 15, 2010 at 12:04 PM, Daniele Dellafiore wrote:
> I have "patched" maven-eclipse-plugin to create an eclipse project also for
> projects with "pom" packaging type.
> I was wondering if this was a bug or a feature and if someone is interested
> in the plugin behaving this way other than
Hi everyone.
I have "patched" maven-eclipse-plugin to create an eclipse project also for
projects with "pom" packaging type.
I was wondering if this was a bug or a feature and if someone is interested
in the plugin behaving this way other than me.
In case, I can work on it and submit a patch.
I
