I had a similar problem in Eclipse (Ganymede) when using Maven and Subclipse plugins. I have not determined which plugin caused this problem, but I suspect that it is related to my pom.xml containing nested modules (i.e. a <modules><module>main-module</module><module>integration-test</module> ). They appear in Eclipse as subfolders with their own pom.xml files (I did not use the Multiple Projects plugin, although I installed it).
I assume that one of the plugins set the derived flag in these folders incorrectly when I checked the SVN project and then updated the MVN dependencies and project parameters.
When I right-click on the properties in the directories of the top-level nested modules, I see that the Derived flag is checked. Having marked the output flag in the module directories (and instead checked the output flag in the target directories in each submodule), he fixed the Open Resource functionality.
Since the derived flag is inherited from directories, you may need to check all your directories in the hierarchy to find the culprit.
If this helps the plugin authors, my top-level module directories contain a hyphen '-' in their names. Perhaps this throws out one of the plugins.
Alex
source share