| Summary: | Changing settings.xml not taken into account | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Pascal Rapicault <pascal> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | igor |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Pascal Rapicault
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. |