[jbosstools-issues] [JBoss JIRA] (JBIDE-25665) It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update

It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update ------------------------------------------------------------------------------ Key: JBIDE-25665 URL: https://issues.jboss.org/browse/JBIDE-25665 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.5.2.Final Reporter: Lukáš Valach Assignee: Nick Boldt Fix For: 4.5.3.AM1 Attachments: CheckForUpdates.png, CheckForUpdates_after_fix.png It is not possible to update to 4.5.2.Final using "Check for Update". Check for Update is not able to find any remedy for this conflict: {code} Cannot complete the install because of a conflicting dependency. Software being installed: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426) Software currently installed: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704) Only one of the following can be installed at once: JBoss WebServices Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.ui 2.0.0.v20180105-1426) JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.ui 1.9.101.v20170822-1704) Cannot satisfy dependency: From: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704) To: org.jboss.tools.ws.ui [1.9.101.v20170822-1704] Cannot satisfy dependency: From: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426) To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426] {code} !CheckForUpdates.png|thumbnail! It is maybe caused by separation of SOAP from jbosstools-webservices (JBIDE-24880). This process is routinely tested and the test passed on Friday/Monday, but unfortunately I made a mistake. I installed JBT 4.5.1 from Eclipse Marketplace, then I added staging update site and executed Check for Update which passed without any problems. But I didn't realize that JBT 4.5.1 added stable update site for 4.5.1, which was used together with 4.5.2 update site, so it was able to resolve that conflict. So I apologize for this issue.