February 2020 - jbosstools-issues

[JBoss JIRA] (JBIDE-27055) Switch to Forge 3.9.6

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-27055: ---------------------------------- Summary: Switch to Forge 3.9.6 Key: JBIDE-27055 URL: https://issues.redhat.com/browse/JBIDE-27055 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Affects Versions: 4.14.0.AM1 Reporter: Jeff MAURY Assignee: Jeff MAURY Fix For: 4.14.0.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-27054: ------------------------------------- Sprint: devex #180 Feb/Mar 2020 > 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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-27054: ------------------------------------- Attachment: (was: 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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] 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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-27054: ------------------------------------- Attachment: 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, screenshot-1.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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim commented on JBIDE-27054: ------------------------------------------ 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, screenshot-1.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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-27054: ------------------------------------- Labels: openshift-restclient-java (was: ) > 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 > Priority: Major > Labels: openshift-restclient-java > Fix For: 4.14.0.Final > > Attachments: image-2020-02-17-16-52-26-938.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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim reassigned JBIDE-27054: ---------------------------------------- Assignee: André Dietisheim > 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 > > > 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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim updated JBIDE-27054: ------------------------------------- Fix Version/s: 4.14.0.Final > 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 > > > 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)

6 years, 1 month

1
0
0 / 0

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

by André Dietisheim (Jira)

[ https://issues.redhat.com/browse/JBIDE-27054?page=com.atlassian.jira.plug... ] André Dietisheim commented on JBIDE-27054: ------------------------------------------ This is caused by https://github.com/openshift/openshift-restclient-java/issues/437 > 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 > > > 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)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2020