[jbosstools-issues] [JBoss JIRA] (JBIDE-27054) When publishing errors, paths reported are not helpful

[André Dietisheim (Jira)]

    [ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974063#comment-13974063 ] 

André Dietisheim edited comment on JBIDE-27054 at 2/17/20 12:16 PM:
--------------------------------------------------------------------

After the fix in the library, the paths are reported correctly:
 !image-2020-02-17-18-16-42-076.png! 


was (Author: adietish):
After the fix in the library, the paths are reported correctly:
 !screenshot-1.png! 

> When publishing errors, paths reported are not helpful
> ------------------------------------------------------
>
>                 Key: JBIDE-27054
>                 URL: https://issues.redhat.com/browse/JBIDE-27054
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.14.0.AM1
>            Reporter: André Dietisheim
>            Assignee: André Dietisheim
>            Priority: Major
>              Labels: openshift-restclient-java
>             Fix For: 4.14.0.Final
>
>         Attachments: image-2020-02-17-16-52-26-938.png, image-2020-02-17-18-16-42-076.png
>
>
> When publishing local code changes to a pod errors, the exact paths (to & from) should be reported. Unfortunately those are currently reported as java object ids which isn't helpful at all
> steps:
> # ASSERT: have an application running on OpenShift
> # ASSERT: have local code for it
> # ASSERT: have a server adapter for publishing local changes 
> # ASSERT: make sure syncing will fail. Ex. kill the app
> # EXEC: hit "Publish" on your server adapter
> # ASSERT: publishing fails
> # EXEC: display the error details
> Result:
>  !image-2020-02-17-16-52-26-938.png! 
> The paths are reported as java object id's which isn't helpful at all.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)