Re: [m2e-users] Problem with "Update Project Configuration" option

[Greg Thomas <greg.d.thomas@xxxxxxxxx>]

For whatever reason, an in-place upgrade doesn't seem to work when
moving to Indigo/m2e-1.x.

The easiest way I've found to resolve it is to simply delete the
project from your Eclipse workspace (without deleting the underlying
files), deleting the Eclipse-related files (.settings\, project, ,
.classpath) and then re-importing the project as a Maven project.

Greg

On 30 November 2011 13:56, Allan Todd <other@xxxxxxxxxxxxxxxxxx> wrote:
> I have a problem with the "Maven -> Update Project Configuration" option
> since upgrading to Indigo.  Rather than working as it used to in m2eclipse,
> it now seems to do the same as "Update Dependencies" option above.
>
> With both Galileo and Indigo I have found that when I import maven projects
> they do not always work correctly.  Specifically they are sometimes not
> recognised as Java projects (I don't get a little 'J' on the folder icon)
> and when I open a Java source file none of the eclipse Java features are
> available (code completion, hyperlinking to methods / classes, etc).  This
> has never been a problem in the past as "Maven -> Update Project
> Configuration" fixes it.  However now this option appears to invoke the
> wrong thing so I'm stuck.
>
> Any advice much appreciated.
>
> Thanks,
>
> Allan
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>