[
https://issues.jboss.org/browse/JBDS-4364?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-4364:
----------------------------------
So... RHSCL contains org.testng.eclipse 6.9.13, but we have something newer in Central.
Why is that a problem?
Central is designed to be able to provide newer 3rd party deps than the platform.
Are you saying we need to push TestNG 6.11 into RHSCL 2.4, so that Central and RHEL 7 have
the same version? If so, the version in Central becomes unnecessary. :)
cc: [~mat.booth]
Conflict org.testng.eclipse 6.9.13. vs 6.11.0.
----------------------------------------------
Key: JBDS-4364
URL:
https://issues.jboss.org/browse/JBDS-4364
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: rpm
Affects Versions: 10.4.0.AM3
Environment: OS: RHEL7
RHSCL:
http://download.eng.brq.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1.0/compos...
Devstudio: rh-eclipse46-devstudio 10.4-0.20170421.0123.el7
Reporter: Lukáš Valach
Assignee: Nick Boldt
Fix For: 10.4.0.GA
It is possible to update TestNG via RH Central.
# RH Central -> Software/Update
# Enable Early Access
# *Show installed*
# Find "TestNG" there is written "Installed, update available"
# Select TestNG and install updates
# Restart
# Then this error message will appear in the log:
{code}
!ENTRY org.testng.eclipse 4 0 2017-04-21 05:21:07.715
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.testng.eclipse [1649]
Another singleton bundle selected: osgi.identity;
osgi.identity="org.testng.eclipse"; type="osgi.bundle";
version:Version="6.11.0.201703011520"; singleton:="true"
{code}
Log:
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
Central constains org.testng.eclipse 6.11.0.201703011520, RPM contains
6.9.13.201701201452.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)