[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3981:
----------------------------------
Nope, not a bug. Problem occurred because I had an older version of rh-eclipse46-eclipse-linuxtools-docker installed, which contains 2.0.0, not 2.1.0. Therefore script was NOT removing the three IUs because 2.0.0 != 2.1.0.
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM1
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23165) IllegalArgumentException in New OpenShift Application Wizard
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-23165:
-------------------------------------
Summary: IllegalArgumentException in New OpenShift Application Wizard
Key: JBIDE-23165
URL: https://issues.jboss.org/browse/JBIDE-23165
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.1.Final
Environment: Windows 10 Home
OpenJDK 1.8
Reporter: Denis Golovin
Priority: Minor
Attachments: oc3iare.gif
]{codejava.lang.IllegalArgumentException:
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63)
at org.eclipse.core.runtime.Assert.isLegal(Assert.java:47)
at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$ConnectionAdvancedPropertiesProvider.update(AdvancedConnectionEditor.java:191)
at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:370)
at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121)
at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537)
at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890)
at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177)
at org.eclipse.jface.wizard.WizardDialog.backPressed(WizardDialog.java:404)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:415)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
at org.eclipse.jface.window.Window.open(Window.java:794)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23134) Improve UI of Deployment tab of Runtime Editor
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ]
Catherine Robson commented on JBIDE-23134:
------------------------------------------
I don't think you're going to like my answer...
Honestly I think this issue here is not whether it is a link or a button, but its placement overall. Actions on the table should be ideally be placed in a toolbar-like space above the table. The bottom left of the table near the navigation tabs means this capability is lost on the page, users won't see it, and it distracts and makes it harder for users to see the navigation tabs at the bottom.
So, I would suggest:
ROW: {left aligned} Filter by: [DROPDOWN] {right aligned} Refresh table button
HEADER ROW
1st TABLE ROW
See PatternFly table pattern for the type of row I am discussion above the table with this type of content: http://www.patternfly.org/pattern-library/content-views/table-view/#_
> Improve UI of Deployment tab of Runtime Editor
> ----------------------------------------------
>
> Key: JBIDE-23134
> URL: https://issues.jboss.org/browse/JBIDE-23134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
> Attachments: screenshot-1.png
>
>
> - Refresh table button is really strange
> - there are some grey background around the sections
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23134) Improve UI of Deployment tab of Runtime Editor
by Catherine Robson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23134?page=com.atlassian.jira.plugi... ]
Catherine Robson edited comment on JBIDE-23134 at 9/14/16 5:32 PM:
-------------------------------------------------------------------
I don't think you're going to like my answer...
Honestly I think this issue here is not whether it is a link or a button, but its placement overall. Actions on the table should be ideally be placed in a toolbar-like space above the table. The bottom left of the table near the navigation tabs means this capability is lost on the page, users won't see it, and it distracts and makes it harder for users to see the navigation tabs at the bottom.
So, I would suggest:
ROW: Filter by: [DROPDOWN] (left align) Refresh table button (right align)
HEADER ROW
1st TABLE ROW
See PatternFly table pattern for the type of row I am discussion above the table with this type of content: http://www.patternfly.org/pattern-library/content-views/table-view/#_
was (Author: crobson):
I don't think you're going to like my answer...
Honestly I think this issue here is not whether it is a link or a button, but its placement overall. Actions on the table should be ideally be placed in a toolbar-like space above the table. The bottom left of the table near the navigation tabs means this capability is lost on the page, users won't see it, and it distracts and makes it harder for users to see the navigation tabs at the bottom.
So, I would suggest:
ROW: {left aligned} Filter by: [DROPDOWN] {right aligned} Refresh table button
HEADER ROW
1st TABLE ROW
See PatternFly table pattern for the type of row I am discussion above the table with this type of content: http://www.patternfly.org/pattern-library/content-views/table-view/#_
> Improve UI of Deployment tab of Runtime Editor
> ----------------------------------------------
>
> Key: JBIDE-23134
> URL: https://issues.jboss.org/browse/JBIDE-23134
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM1
>
> Attachments: screenshot-1.png
>
>
> - Refresh table button is really strange
> - there are some grey background around the sections
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Mat Booth (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Mat Booth commented on JBDS-3981:
---------------------------------
Right, but in a comment further up you say you modified the script to remove IUs from the update site mirror if the x.y.z version is the same.
However:
$ rpm -ql rh-eclipse46-eclipse-linuxtools-docker
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/features/org.eclipse.linuxtools.docker.feature.source_2.1.0.201609071048
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/features/org.eclipse.linuxtools.docker.feature_2.1.0.201609071048
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.core.source_2.1.0.201609071048.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.core_2.1.0.201609071048.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.docs.source_2.0.0.201609071048.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.docs_2.0.0.201609071048.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.editor.source_1.0.0.201609071048.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.editor_1.0.0.201609071048.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.ui.source_2.1.0.201609071048.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/linuxtools-docker/eclipse/plugins/org.eclipse.linuxtools.docker.ui_2.1.0.201609071048.jar
$ rpm -qp -l rh-eclipse46-devstudio-1.0-1.el7.x86_64.rpm | grep linuxtools
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.eclipse.linuxtools.docker.feature_2.1.0.201608310043
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.linuxtools.docker.core_2.1.0.201608310043.jar
/opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.eclipse.linuxtools.docker.ui_2.1.0.201608310043.jar
So is this a bug in the script?
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM1
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (ERT-419) Issue in dep resolution with Neon.1 RC3 [EBZ#501222]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-419:
---------------------------------------
Summary: Issue in dep resolution with Neon.1 RC3 [EBZ#501222]
Key: ERT-419
URL: https://issues.jboss.org/browse/ERT-419
Project: Eclipse Release Train
Issue Type: Task
Components: Equinox
Reporter: Friendly Jira Robot
Priority: Critical
We're testing JBoss Tools (built against Neon.0) on Neon.1 RC3 and get an issue that could be a p2 bug. Here is the error message:
```
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
Software currently installed: Eclipse XML Editors and Tools 3.8.0.v201608061842 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201608061842)
Only one of the following can be installed at once:
Eclipse XML Editors and Tools 3.8.0.v201608061842 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201608061842)
Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
Cannot satisfy dependency:
From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
Cannot satisfy dependency:
From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
Cannot satisfy dependency:
From: Eclipse XML Editors and Tools 3.8.0.v201608061842 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201608061842)
To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201608061842]
Cannot satisfy dependency:
From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
```
As you can see on the last lines of this error, the org.jboss.tools.ws.feature.feature.group depends on a wide version range. And the product we're testing is the JS EPP package, which includes version 3.8.1.v201609011813 of this feature (in the range).
I don't really understand what could be another reason for this error, out of a p2 bug. So any hint would be welcome!
Steps to reproduce:
* Get some Neon.1 RC3 package from https://hudson.eclipse.org/packaging/job/neon.epp-tycho-build/ (I use the JS one, but it happens also with the Java and Java EE ones)
* Help > Install New Software > http://download.jboss.org/jbosstools/neon/staging/updates/ > select only "JBoss WebServices Tools"
* Keep "Contact all update sites" ticked to improve probabily of happy installation
* Finish
EXPECTED: installation goes fine
GOT: Error message above that seems inconsistent with my installation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23143:
----------------------------------------
I'm leaning towards leave it as an known issue for 4.4.1 and update our TP for 4.4.2
> Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23143
> URL: https://issues.jboss.org/browse/JBIDE-23143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, updatesite, upstream, webservices
> Affects Versions: 4.4.1.Final
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png
>
>
> When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen.
> !neon-1-remediation.png!
> If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools.
> This is the original error message (third option):
> {code}
> Your original request has been modified.
> "Code Recommenders Snipmatch" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> Only one of the following can be installed at once:
> Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
> Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824)
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
> To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824]
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-23143 at 9/14/16 2:13 PM:
-----------------------------------------------------------------
I'm leaning towards leaving it as an known issue for 4.4.1 and update our TP for 4.4.2
was (Author: akazakov):
I'm leaning towards leave it as an known issue for 4.4.1 and update our TP for 4.4.2
> Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2/RC3 (remediation required)
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-23143
> URL: https://issues.jboss.org/browse/JBIDE-23143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, updatesite, upstream, webservices
> Affects Versions: 4.4.1.Final
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Attachments: jbt4.4.1_on_neon.1.RC3.png, jbt4.4.1_on_neon.1.RC3_disabled_sites.png, jbt4.4.1_on_neon.1.RC3_remediation_needed.png, jbt4.4.1_on_neon.1.RC3_remediation_opt2.png, neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png
>
>
> When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen.
> !neon-1-remediation.png!
> If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools.
> This is the original error message (third option):
> {code}
> Your original request has been modified.
> "Code Recommenders Snipmatch" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> Only one of the following can be installed at once:
> Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
> Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824)
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
> To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824]
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-4049) Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4049?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4049:
--------------------------------------
Yes, I think we should switch to a requirement in 10.2. If we really need to lock down the version of jsdt we should do it on plugin/manifest level.
> Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4049
> URL: https://issues.jboss.org/browse/JBDS-4049
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, target-platform, updatesite, upstream
> Affects Versions: 10.1.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM1
>
> Attachments: ds10.1_on_neon.1.RC3_remediation_needed.png
>
>
> Steps to repro:
> 1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
> 2. Help > Eclipse Marketplace... > Search for "jboss" and install Red Hat JBoss Developer Studio 10.1.0.GA
> 3. Remediation needed:
> {code}Cannot complete the install because of a conflicting dependency.
> Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725)
> Software currently installed: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904)
> Only one of the following can be installed at once:
> JavaScript Development Tools Core 2.0.0.v201603171403 (org.eclipse.wst.jsdt.core 2.0.0.v201603171403)
> JavaScript Development Tools Core 1.3.401.v201511181529 (org.eclipse.wst.jsdt.core 1.3.401.v201511181529)
> JavaScript Development Tools Core 2.0.0.v201608251059 (org.eclipse.wst.jsdt.core 2.0.0.v201608251059)
> JavaScript Development Tools Core 2.0.0.v201604281930 (org.eclipse.wst.jsdt.core 2.0.0.v201604281930)
> JavaScript Development Tools Core 2.0.0.v201605251700 (org.eclipse.wst.jsdt.core 2.0.0.v201605251700)
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725)
> To: com.jboss.devstudio.core.rpm.feature.feature.group [10.1.0.v20160902-1725]
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (RPM Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.rpm.feature.feature.group 10.1.0.v20160902-1725)
> To: org.eclipse.wst.jsdt.feature.feature.group [2.0.0.v201605311817]
> Cannot satisfy dependency:
> From: JavaScript Development Tools 2.0.0.v201605311817 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201605311817)
> To: org.eclipse.wst.jsdt.core [2.0.0.v201605251700]
> Cannot satisfy dependency:
> From: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904)
> To: org.eclipse.wst.jsdt.core [2.0.0.v201608251059]
> {code} -- [^ds10.1_on_neon.1.RC3_remediation_needed.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3981:
----------------------------------
Because something in devstudio requires/includes it, probably.
I can explicitly blacklist things, however.
https://github.com/jbdevstudio/jbdevstudio-product/blob/master/rpm/devstu...
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM1
>
> Attachments: .log, feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, rheclipse_20160901_0937.log.txt, rheclipse_20160901_0950.log.txt, rheclipse_20160901_1720.log.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months