335720 – Add a preference to automatically update configuration

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335720 - Add a preference to automatically update configuration

Summary: Add a preference to automatically update configuration

Status:	RESOLVED FIXED

Alias:	None

Product:	z_Archived
Classification:	Eclipse Foundation
Component:	m2e (show other bugs)
Version:	unspecified
Hardware:	All All

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	Project Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	335710
	Show dependency tree

Reported:	2011-01-28 13:16 EST by Pascal Rapicault
Modified:	2021-04-19 13:23 EDT (History)
CC List:	5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Pascal Rapicault

2011-01-28 13:16:48 EST

We want to explore with adding a preference to automatically refresh project configuration. This preference would be turned off by default.

Comment 1 Igor Fedorenko

2011-08-01 01:19:37 EDT

see also bug 335710

Comment 2 Igor Fedorenko

2013-09-28 21:07:28 EDT

I am keeping this open for future reference, but this is WONTIFX

Comment 3 Fred Bricon

2014-11-07 16:39:33 EST

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/

Comment 4 Fred Bricon

2015-03-13 08:55:04 EDT

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?

Comment 5 Fred Bricon

2015-03-18 02:27:25 EDT

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

Comment 6 Greg Amerson

2015-03-18 02:51:19 EDT

+1

Comment 7 Fred Bricon

2015-03-18 08:09:15 EDT

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

Comment 8 Fred Bricon

2015-03-24 17:53:50 EDT

Given the endless build loops Anton experienced (bug #462898), I've switched the default  activation value to disabled in M6

Comment 9 Denis Roy

2021-04-19 13:23:52 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/