Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361486 - NullPointerException when trying to publish comments
Summary: NullPointerException when trying to publish comments
Status: RESOLVED DUPLICATE of bug 349023
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-19 19:35 EDT by Alex Blewitt CLA
Modified: 2011-10-20 05:38 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Blewitt CLA 2011-10-19 19:35:05 EDT
Build Identifier: Eclipse 3.7.1 with Mylyn Reviews 0.8.2

I tried to publish comments to the Gerrit server (with development_become_any_account with username but empty password) and I got a nullpointerexception in the log:

java.lang.NullPointerException
	at com.google.gerrit.common.data.PatchSetPublishDetail.getAllowed(PatchSetPublishDetail.java:96)
	at org.eclipse.mylyn.internal.gerrit.ui.operations.PublishDialog.doRefresh(PublishDialog.java:128)
	at org.eclipse.mylyn.internal.gerrit.ui.operations.GerritOperationDialog.createDialogArea(GerritOperationDialog.java:137)
	at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:155)

I should be allowed to publish comments (and can do using the same user via the Gerrit interface). There doesn't seem to be anything else associated with it.

Reproducible: Didn't try

Steps to Reproduce:
I can easily repeat this problem but I'm using Gerrit 2.2.1 with Mylyn Reviews 0.8.2 and a development_become_any_account. I can load the review and drill into it (including adding comments - and the adding comments works, because there's a draft that gets saved on the server when I add it in-line). When I click on the 'publish comments' button I get this error message.
Comment 1 Steffen Pingel CLA 2011-10-20 05:38:53 EDT
Should have been fixed by bug 349023. Please reopen if you are still experiencing the error after updating to the latest weekly build.

*** This bug has been marked as a duplicate of bug 349023 ***