Bug 521955 - NPEs when turn on check-for-updates
Summary: NPEs when turn on check-for-updates
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2017-09-06 14:37 EDT by Randy Strauss CLA
Modified: 2019-11-10 15:38 EST (History)
1 user (show)

See Also:


Attachments
2 windows- my update settings, all the errors with NPE details (each says NPE an no more) (504.70 KB, image/png)
2017-09-06 14:37 EDT, Randy Strauss CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Randy Strauss CLA 2017-09-06 14:37:45 EDT
Created attachment 270102 [details]
2 windows- my update settings, all the errors with NPE details (each says NPE an no more)

I changed 

I restarted eclipse and get a window with about 30 1-line errors. Over half just say "Resolver"
Clicking on any one gives a line like:

An internal error occurred during: "Load https://raw.githubusercontent.com/m2e-code-quality/m2e-code-quality/master/m2e-code-quality.setup".
java.lang.NullPointerException

See the attached screenshot for the list of errors and my update settings.

I restarted eclipse 3 times, and each time got the errors.  Then I started this bug report.  Now I've tried again and it starts fine.

Except, at the bottom it says "TeamCity Delayed Login" - I don't know if that used to appear...

And it's not updating.  I'm running Neon and supposedly Oxygen is available.
sigh...

PS: MacOSX 10.12.6, eclipse 4.6.3
Should I just download Oxygen?  sigh...
Comment 1 Randy Strauss CLA 2017-09-06 14:38:38 EDT
No additional comments- your form just made me insert the image twice...
Comment 2 Dani Megert CLA 2017-11-13 10:15:41 EST
Please provide the full .log.
Comment 3 Eclipse Genie CLA 2019-11-10 15:38:20 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.