[
https://issues.jboss.org/browse/JBDS-4194?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-4194:
----------------------------------
{quote}Suspect the problem is that Eclipse isn't sure if these features are
"installed" or "dropped in" and so doesn't have all the correct
metadata available. But as I said, I can't figure out how to force the migration
wizard to appear on startup... so... unless we can pregenerate the metadata that needs to
be generated as part of the rpm install, I don't know what else to guess here.{quote}
After discussion w/ Alexey today, I don't think this is really a problem. The
install/upgrade path for rpm users is to run `yum update rh-eclipse46-devstudio` not `Help
> Check for Updates`.
So while it's an annoyance when you're used to looking for updates within Eclipse
rather than from your package manager of choice, for RHSCL users I suspect this is a
non-issue. [~akazakov] If you agree, can you close this issue?
If not, we can revisit it for RHSCL 2.4 / devstudio 10.3. Please advise.
Devstudio isn't able to discover updates
----------------------------------------
Key: JBDS-4194
URL:
https://issues.jboss.org/browse/JBDS-4194
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Affects Versions: 10.2.0.GA
Environment: RHEL7
Reporter: Lukáš Valach
Priority: Critical
Attachments: devstudio-ootb-update-sites-after-pinging-Central.png,
devstudio-ootb-update-sites.png
Devstudio isn't able to discover updates. When I use *Help->Check For Updates*
then I get "No updates were found" message.
I used this as update site:
https://devstudio.redhat.com/10.0/snapshots/updates/
Tested in 10.2-0.20161121.0756.
Some suggestions and possible workaround are in JBDS-4184.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)