| Summary: | Add a preference to automatically update configuration | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Pascal Rapicault <pascal> |
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | fbricon, gregory.amerson, igor, robert.munteanu, stephen.k.cooper |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 335710 | ||
|
Description
Pascal Rapicault
see also bug 335710 I am keeping this open for future reference, but this is WONTIFX FYI, I whipped up a small plugin that automatically update out-of-date project configuration, under our JBoss Tools Playground repo [1]. I'm not sure if it's completely safe to use. There's no preference to (de)activate it -yet-. The plugin is set to start on workspace startup for now, which isn't ideal, but if you deactivate it from Preferences > Startup and Shutdown and restart the workspace, it should be inactive. It's, most probably, sub-optimally implemented, but it worked on the small set of projects I tried. p2 site to install it from is at [2]. Feel free to try it and give some feedback. Then we can discuss whether it can be contributed back to m2e. [1] https://github.com/jbosstools/jbosstools-playground/tree/master/plugins/org.jboss.tools.playground.maven.autoupdate [2] http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground_master/all/repo/ I ported the playground code to m2e-core, adding a global preference to turn it on/off (off by default) The core of the change is in m2e ui, since the resource change listener detecting out-of-date projects needs to call org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob Gerrit changeset https://git.eclipse.org/r/#/c/43787/ Test : https://github.com/tesla/m2e-core-tests/pull/32 wdyt? By popular demand, pushed new changeset to turn the autoupdate on by default https://git.eclipse.org/r/#/c/43787/3/org.eclipse.m2e.core/src/org/eclipse/m2e/core/internal/preferences/MavenPreferenceInitializer.java +1 Applied in master http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=6eb6db0ce9f1f9169406f2d9846c09b84477a909 Tests https://github.com/tesla/m2e-core-tests/commit/48ddc4d0bfa79bf9f48ef854175110c122501f5f The preference has been turned on by default : http://screencast.com/t/jOGEL5tt Given the endless build loops Anton experienced (bug #462898), I've switched the default activation value to disabled in M6 |