This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Got this reported from JDev with comment "Tried to attach a patch to a Task". com.tasktop.c2c.server.common.service.AuthenticationException: UNAUTHORIZED at com.tasktop.c2c.server.common.service.web.ApacheResponseErrorHandler.handleError(ApacheResponseErrorHandler.java:105) at com.tasktop.c2c.server.common.service.web.ApacheHttpRestClientDelegate.postForObject(ApacheHttpRestClientDelegate.java:242) at com.tasktop.c2c.server.tasks.service.TaskServiceClient$PostCall.doCall(TaskServiceClient.java:304) at com.tasktop.c2c.server.tasks.service.TaskServiceClient.saveAttachment(TaskServiceClient.java:464) at o.eclipse.tools.cloud.dev.tasks.CloudDevClient.postAttachment(CloudDevClient.java:240) at o.eclipse.tools.cloud.dev.tasks.CloudDevTaskAttachmentHandler.postContent(CloudDevTaskAttachmentHandler.java:50) at org.netbeans.modules.mylyn.util.commands.PostAttachmentCommand.execute(PostAttachmentCommand.java:97) at org.netbeans.modules.odcs.tasks.ODCSExecutor.execute(ODCSExecutor.java:86) at org.netbeans.modules.odcs.tasks.ODCSExecutor.execute(ODCSExecutor.java:77) at org.netbeans.modules.odcs.tasks.issue.ODCSIssue.addAttachment(ODCSIssue.java:623) at org.netbeans.modules.odcs.tasks.issue.ODCSIssue.attachPatch(ODCSIssue.java:585) at org.netbeans.modules.odcs.tasks.ODCSIssueProvider.attachFile(ODCSIssueProvider.java:105) at org.netbeans.modules.odcs.tasks.ODCSIssueProvider.attachFile(ODCSIssueProvider.java:56) at org.netbeans.modules.bugtracking.IssueImpl.attachFile(IssueImpl.java:175) at org.netbeans.modules.bugtracking.api.Issue.attachFile(Issue.java:280) ...
Again wrapped in a com.tasktop.c2c.server.common.service.WrappedCheckedException. ODCSExecutor.execute() catches RuntimeException but then logs it as SEVERE?
> Again wrapped in a com.tasktop.c2c.server.common.service.WrappedCheckedException. > ODCSExecutor.execute() catches RuntimeException but then logs it as SEVERE? runtime is nasty and severe seemed to be appropriate back than before the client started throwing RE on authentication problems (on top of it, that it maybe even aren't real auth problems)
*** This bug has been marked as a duplicate of bug 244688 ***