Community
Participate
Working Groups
Steps to reproduce: - Fire up eclipse - Import the following project org.eclipse.m2e.tests/projects/lifecyclemapping/lifecycleMappingMetadata/PluginExecutionActionsTest/testMojoExecutionErrorWithMessage - Notice the error - change the settings.xml to be the one in org.eclipse.m2e.tests/settings.xml - Go back to the project, you will notice that the error is still there and still referring to RSO. I have tried to clean, the project and the error does not work. the only way to get rid of the error is to delete the project and reimport it. When I point to a different settings.xml I would expect things to be rebuilt automatically or at least don't want to have to delete and import to get rid of an error
Can you check if (right-click)->Maven->UpdateDependencies makes the problem go away?
Yes, doing update dependencies make it go away. Should we prompt the user when the settings.xml is changed?
Changes to settings.xml can change everything. Ideally, we need to completely re-resolve all dependencies and update configuration of all projects. Again ideally, we also need to monitor out-of-workspace changes to settings.xml and do the same complete update of everything.
As explained in comment 3, automatically and correctly reflecting changes to settings.xml is not practically possible.
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
