Skip to content
This repository has been archived by the owner on Dec 9, 2018. It is now read-only.

Easier access to refreshing repository contents #404

Closed
njbartlett opened this issue May 18, 2012 · 5 comments
Closed

Easier access to refreshing repository contents #404

njbartlett opened this issue May 18, 2012 · 5 comments
Assignees
Milestone

Comments

@njbartlett
Copy link
Member

Need to refresh plugins when remote repo contents changes, but when?

Options:

  1. Manually: menu entry to reload plugins.
  2. Automatically when a build start? Perhaps on FULL_BUILD, then can trigger with clean?
  3. Poll continuously. How? And what do we do when we detect a change... prompt to rebuild?
@derheld42
Copy link
Contributor

Just an idea.. but maybe make it user configurable? Perhaps always enable a manual means, and then allow #2 or #3 depending on a user's needs.

I know I'm interested in having #1 right now... Currently I wouldn't use #2 or #3, however, I could see #3 being useful and perhaps in certain types of testing could make #2 very useful too.

@derheld42
Copy link
Contributor

I've found several cases where I've wanted to refresh just a single repo in the last couple months. The bndtools menu refresh repos option works. But it refreshes all repos and it blocks the foreground thread. (Yup, I made that change, but it needs to be improved)

@pkriens
Copy link
Member

pkriens commented Sep 24, 2014

Why not add a menu on the repo? This is quite easy to do, implement Map<String,Run> actions(Object[]type) in the repo.

@pkriens
Copy link
Member

pkriens commented Sep 24, 2014

I've added a Refresh menu in FixedIndexRepo

@pkriens pkriens closed this as completed Sep 24, 2014
@pkriens
Copy link
Member

pkriens commented Sep 24, 2014

2fba8ddcc6 ([repos] #404 Delete entry menu on the FixedIndexedRepo and a Refresh menu entry on FixedIndexed and LocalIndexed Repos )

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants