Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add capability to reload IUs from defined locations #33

Open
hegewald opened this issue Jul 2, 2014 · 8 comments
Open

Add capability to reload IUs from defined locations #33

hegewald opened this issue Jul 2, 2014 · 8 comments
Assignees

Comments

@hegewald
Copy link

hegewald commented Jul 2, 2014

It would be a great feature to have the possibility to force a reload of the available IU versions of the defined locations.

In the actual version we face a problem with new deployed versions of an IUs in one of the defined locations.
If we generate the .target file after the deployment the generated .target file didn't contains the new deployed version of the IU.

Until now the only chance to get the new version is to restart Eclipse and regenerate the .target file.

@mbarbero
Copy link
Member

mbarbero commented Jul 2, 2014

Thank you for your feedback. This cache has actually been introduced in 2.1.0. I thought about the reload issue but didn't really succeed in finding a good way to do that. I was actually expecting p2 to be clever enough to see that the remote repository has changed and then update its cache, but it does not. Maybe I should subclass MetadataRepositoryManager to add this check. Other solution (simpler) would be to add a reload action somewhere. The question is where: on the contextual menu of the .tpd file? On a location within a .tpd file? What do you think?

@hegewald
Copy link
Author

hegewald commented Jul 2, 2014

In most of our use cases we now which location needs a reload, therefore i think a reload on a location is ok.
Nevertheless i think an reload on the complete file is a valid use case too, so both solutions are reasonable.

@mbarbero mbarbero added this to the 2.2.0 — notorious-angry milestone Jul 2, 2014
@mbarbero mbarbero self-assigned this Jul 2, 2014
@mbarbero
Copy link
Member

mbarbero commented Jul 2, 2014

Ok. Thank you. I will work in that direction then.

I label it as an enhancement and it will be part of the next milestone.

@hegewald
Copy link
Author

hegewald commented Jul 2, 2014

OK, great, thanks.

@dzonekl
Copy link

dzonekl commented Sep 8, 2014

+1, run into cached old P2.

@toshovski
Copy link

Not sure if that's the same issue, but when I add new sources to a composite repository, They are not recognized from the targetplatform editor. I need to restart eclipse in order to clear the cache... A Button might be also useful, that clears the cache..

@mbarbero mbarbero removed this from the 2.2.0 — notorious-angry milestone Sep 5, 2018
@col-panic
Copy link

Any progress on this? (just being in the situation once again ...) thanks

@col-panic
Copy link

Just searched for this again :) Reworked our target and re-built the p2 sites to satisfy the dependencies ... every time the p2 site changed I had to restart Eclipse to get the updated state in the tpd view. This really eats time ...

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

No branches or pull requests

5 participants