[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-23143 at 9/8/16 5:30 AM: ---------------------------------------------------------------- [The error message on 3rd option is always the best thing to show when reporting such error] The issue is that some content of our TP (org.eclipse.wst.web_ui.feature) are still in the Neon.0 version which has dependencies conflicting with the Neon.1. Possible fix is obviously to have our TP referencing Neon.1, so it would be compatible with Neon.1, and users of Neon.0 will see there WTP version updated as they install JBoss Tools. However, here are a few reasons why I believe it's better to not panic: * Here, it seems to me that you did untick the "Contact all software sites..." checkbox at install or disabled Eclipse Neon (milestones) repository from available sites. Do you confirm? If so, the regular user (who has Neon repo and keep the "Contact all software sites..." ticked) should have installation working correctly as it would resolve org.eclipse.wst.web_ui.feature to the version in the Neon repo. * The remediation does a pretty good suggestion when selecting "Update my installation". So overall, the likelyhood for this issue to happen seems low, the workaround is easy and good, and the issue will vanish as soon as we link to a Neon.1 target-platform. was (Author: mickael_istria): [The error message on 3rd option is always the best thing to show when reporting such error] The issue is that some content of our TP (org.eclipse.wst.web_ui.feature) are still in the Neon.0 version which has dependencies conflicting with the Neon.1. Possible fix is obviously to have our TP referencing Neon.1, so it would be compatible with Neon.1, and users of Neon.0 will see there WTP version updated as they install JBoss Tools. However, here are a few reasons why I believe it's better to not panic: * Here, it seems to me that you did untick the "Contact all software sites..." checkbox at install or disabled Eclipse Neon (milestones) repository from available sites. Do you confirm? If so, the regular user -who has Neon repo and keep the "Contact all software sites..." ticked- should have installation working correctly as it would resolve org.eclipse.wst.web_ui.feature to the version in the Neon repo. * The remediation does a pretty good suggestion when selecting "Update my installation". So overall, the likelyhood for this issue to happen seems low, the workaround is easy and good, and the issue will vanish as soon as we link to a Neon.1 target-platform. -- This message was sent by Atlassian JIRA (v6.4.11#64026)