Bug 543874 - Unable to install TestNG in to eclipse
Summary: Unable to install TestNG in to eclipse
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 4.11   Edit
Hardware: PC Windows 10
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-28 00:27 EST by Nandeeswar Porla CLA
Modified: 2023-01-09 15:49 EST (History)
0 users

See Also:

Attachments
attachment for TestNG issue (268.60 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2019-01-28 00:27 EST, Nandeeswar Porla CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nandeeswar Porla CLA 2019-01-28 00:27:21 EST 
Created attachment 277318 [details]
attachment for TestNG issue

Error description:

 An error occurred while collecting items to be installed
session context was:(profile=epp.package.php, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Unable to read repository at http://cucumber.github.com/cucumber-eclipse/update-site/plugins/cucumber.eclipse.steps.integration_0.0.23.201811220126.jar.
Read timed out

Eclipse version: Neon(4.6.0)
Windows 10 Operating system.
Comment 1 Eclipse Genie CLA 2021-01-18 01:06:35 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-01-09 15:49:09 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.