Opened 4 years ago

Last modified 4 years ago

#19211 new enhancement

Plugin update interval: Allow to set zero to always update on startup

Reported by: skyper Owned by: team
Priority: minor Milestone:
Component: Core Version:
Keywords: template_report update plugin interval Cc:


What steps will reproduce the problem?

  1. In Preferences -> Plugins -> Plugins update policy: set interval to zero 0 and radio button to "ask before update" on time period.
  2. Close preferences and restart

What is the expected result?

A dialog with a message asking to update the plugins

What happens instead?

No dialog and the interval in preferences is set to default, 30 days.

Please provide any additional information below. Attach a screenshot if possible.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-05-05 08:59:02 +0200 (Tue, 05 May 2020)
Build-Date:2020-05-05 11:40:03

Attachments (0)

Change History (8)

comment:1 by stoecker, 4 years ago

Owner: changed from team to skyper
Status: newneedinfo

Why should this be necessary?

Last edited 4 years ago by stoecker (previous) (diff)

comment:2 by skyper, 4 years ago

If latest is not updated once a day I have to always manually start the process under preferences and restart instead of being ask on startup with manual decision and without restart. Right now 1 is the lowest value which is usually two days. Thish is too long in my opinion.

comment:3 by stoecker, 4 years ago

Why do you need to check for plugins that often?

in reply to:  3 comment:4 by skyper, 4 years ago

Replying to stoecker:

Why do you need to check for plugins that often?

I would like to check every eight or twelve hours but not every day plus 0 to 23 hours. The easiest way, would be to be ask and reminded every time to manually choose but I would be happy with smaller values than 1.

comment:5 by stoecker, 4 years ago

You did not answer the why. Plugins don't change that often and a JOSM version update already triggers a refresh, so why?

comment:6 by skyper, 4 years ago

I usually run latest and want to have newest plugin version installed.
Just look at the last days. I would have had to wait two by chance almost three days to get the updates for mapillary or utilsplugin2.

I do not want to restart after plugin update, so it needs to be done within startup.

A new command line option "--update-plugins" would also work for me.

comment:7 by GerdP, 4 years ago

If we change something here please make sure that it is still possible to use a locally compiled version. My current workflow when working on plugins is this:

  1. use ant clean dist in the plugin directory
  2. copy the new binary into JOSMs plugin directory
  3. start JOSM
  4. check if JOSM replaced my binary with an older version, if yes, stop JOSM, goto 2.
  5. start debugging in Eclipse

IIGTR JOSM replaces the binary only once per day, but when it happens it can be really confusing. If there is a better way to do this, please let me know. My settings:

pluginmanager.time-based-update.interval	30
pluginmanager.time-based-update.policy	ask
pluginmanager.version-based-update.policy	always

comment:8 by skyper, 4 years ago

Owner: changed from skyper to team
Status: needinfonew

Yesterday, I ran into the situation again. Manual update did not work, see #19006.

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to skyper.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.