This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | [69cat] Externally added Gems are not properly updated by platform manager | ||
---|---|---|---|
Product: | ruby | Reporter: | esmithbss <esmithbss> |
Component: | Gems | Assignee: | issues@ruby <issues> |
Status: | NEW --- | ||
Severity: | normal | CC: | emononen |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
esmithbss
2010-03-17 06:58:25 UTC
Thanks for the report. The wizard should already reload the local gems, but I think GEM_HOME and GEM_PATH are cached (the IDE passes them to the gem tool when running it). In your case one of those env variables changed, right? As a workaround removing and then re-adding the platform should help. I have to think about how to refresh platform info (GEM_HOME etc) automatically when needed. It is not entirely straightforward as computing the info may take quite long, and also have to consider whether (and how) to preserve any possible user changes in platform config. Maybe an explicit (platform specific) reset action in the platform manager would be enough.. Yes, the GEM_PATH changes when you update the gems in the way I've outlined. I found the unload and re-autodetect the platforms last night. Thank you for confirming this as the way to get around this problem. Is it possible to do something on a relaunch of the IDE. Something that could "verify" the existance of the paths and configurations within the cache, then report the issues and recommended fixes. Note: This is not a deep dive into the cache to re-verify everything. A path check or test which is rather fast should suffice. What you propose sounds like a good solution, will implement something along those lines (not sure whether for 6.9 though). *** Bug 145771 has been marked as a duplicate of this bug. *** |