[JBoss JIRA] (JBDS-4357) Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4357:
----------------------------------
Best way to figure out where IUs come from is to use the p2browser [1] (as you did) and then load up all the update sites that appear in ide-config.properties (as you did too) *AND* in your Eclipse/devstudio installation (that's the missing piece!).
!m2e171.png|thumbnail!
[1] https://github.com/ifedorenko/p2-browser
So, the older version is coming from devstudio sites: org.eclipse.m2e.feature.feature.group *1.7.1.20161104-1805*.
And the newer version is coming from here [2]. Since it's a droplet and not an update site, p2browser can't browse it.
[2] /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/m2e-core/eclipse/features/org.eclipse.m2e.feature_1.7.1.20170214-1514
> Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-4357
> URL: https://issues.jboss.org/browse/JBDS-4357
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM3
> Environment: RHSCL: http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1....
> Devstudio: 10.4-0.20170410.1402.el7
> OS: Fedora24 and RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: m2e171.png, rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt
>
>
> I tried to install stuff form RH Central manually to verify if automated tests are reliable and I found this problem which automated test didn't catch.
> When I installed "JBoss Tools Maven Packaging Configurator" I got bundle exceptions related to org.eclipse.m2e.*, see the log:
> [^rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt]
> It seems that central contains org.eclipse.m2e 1.7.1.20161104-1805 but in Devstudio RPM is installed 1.7.1.20170214-1514.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4357) Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4357 at 4/25/17 1:27 PM:
-----------------------------------------------------------
Best way to figure out where IUs come from is to use the p2browser [1] (as you did) and then load up all the update sites that appear in ide-config.properties (as you did too) *AND* in your Eclipse/devstudio installation (that's the missing piece!).
!m2e171.png|thumbnail!
[1] https://github.com/ifedorenko/p2-browser
So, the older version is coming from devstudio sites: org.eclipse.m2e.feature.feature.group *1.7.1.20161104-1805*.
And the newer version is coming from here [2]. Since it's a droplet and not an update site, p2browser can't browse it.
[2] /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/m2e-core/eclipse/features/org.eclipse.m2e.feature_*1.7.1.20170214-1514*
was (Author: nickboldt):
Best way to figure out where IUs come from is to use the p2browser [1] (as you did) and then load up all the update sites that appear in ide-config.properties (as you did too) *AND* in your Eclipse/devstudio installation (that's the missing piece!).
!m2e171.png|thumbnail!
[1] https://github.com/ifedorenko/p2-browser
So, the older version is coming from devstudio sites: org.eclipse.m2e.feature.feature.group *1.7.1.20161104-1805*.
And the newer version is coming from here [2]. Since it's a droplet and not an update site, p2browser can't browse it.
[2] /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/m2e-core/eclipse/features/org.eclipse.m2e.feature_1.7.1.20170214-1514
> Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-4357
> URL: https://issues.jboss.org/browse/JBDS-4357
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM3
> Environment: RHSCL: http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1....
> Devstudio: 10.4-0.20170410.1402.el7
> OS: Fedora24 and RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: m2e171.png, rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt
>
>
> I tried to install stuff form RH Central manually to verify if automated tests are reliable and I found this problem which automated test didn't catch.
> When I installed "JBoss Tools Maven Packaging Configurator" I got bundle exceptions related to org.eclipse.m2e.*, see the log:
> [^rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt]
> It seems that central contains org.eclipse.m2e 1.7.1.20161104-1805 but in Devstudio RPM is installed 1.7.1.20170214-1514.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4357) Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4357?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4357:
-----------------------------
Attachment: m2e171.png
> Conflict org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 vs 1.7.1.20170214-1514
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-4357
> URL: https://issues.jboss.org/browse/JBDS-4357
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM3
> Environment: RHSCL: http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1....
> Devstudio: 10.4-0.20170410.1402.el7
> OS: Fedora24 and RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: m2e171.png, rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt
>
>
> I tried to install stuff form RH Central manually to verify if automated tests are reliable and I found this problem which automated test didn't catch.
> When I installed "JBoss Tools Maven Packaging Configurator" I got bundle exceptions related to org.eclipse.m2e.*, see the log:
> [^rh-eclipse46-devstudio10.4-0.20170410.1402.el7.log.20170410-1722_strict.txt]
> It seems that central contains org.eclipse.m2e 1.7.1.20161104-1805 but in Devstudio RPM is installed 1.7.1.20170214-1514.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23422:
------------------------------------
This keeps being punted out. Any chance it'll be fixed in the last sprint before 4.4.4.Final and we're (hopefully) all done forever with Neon.x releases?
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.4.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months