Description Stephen Cooper 2011-07-27 14:27:53 EDT

If a project is checked in with a dependency which cannot be resolved, e.g. a SNAPSHOT which the user doesn't have locally and which has been removed from the central repository, then checking out the project results in Eclipse losing knowledge of the fact that the project was checked out from subversion.

This has been a nagging issue for years/multiple releases of m2eclipse/m2e. Only now figured out the cause.

Here's my current configuration where I can reliably re-create the issue:
Mac OS X 10.7
Eclipse 3.7 Indigo 20110615-0604
m2e 1.0.0.20110607-2117
Subversive SVN Team Provider (Incubation) 0.7.9.I20110724-1700
SVNKit 1.3.5 r7406

However, this has been created on linux and Windows as well, and in versions 3.5 and 3.6 of eclipse as well.

Steps to re-create:
Outside of eclipse, create a project with a dependency on a SNAPSHOT which does not exist. Check in that project to SVN.
Inside eclipse, enable SVN label decorations to more easily see the problem.
Chose to Check out as Maven project in the SVN repository explorer
Once the check-out is complete, notice that the SVN version decorations do not appear. Also notice that under the Team menu there are no SVN commands, only e.g. apply a patch

Steps to work-around:
Fix the pom.xml to reference a valid dependency
Delete the project without deleting from the file system
Import existing maven project
Notice that the SVN label decorations are visible for the project.

I get the same issue regardless of if I check out as a maven project or import existing maven project. I chose to report the bug against m2e instead of against subversive because repairing the pom resolves the issue.