February 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-25697) Improve error message when resource does not exist

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25697?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25697: ---------------------------------- Attachment: Screenshot_20180209_104512.png > Improve error message when resource does not exist > -------------------------------------------------- > > Key: JBIDE-25697 > URL: https://issues.jboss.org/browse/JBIDE-25697 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM1 > Reporter: Josef Kopriva > Attachments: Screenshot_20180209_104512.png > > > Steps to reproduce: > 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer > 2. EXEC: Right click on project -> New -> Resource... > 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) > 4. EXEC: hit Finish > 5. Error message is not shown correctly and it shows stacktrace: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25697) Improve error message when resource does not exist

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25697?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25697: ---------------------------------- Description: Steps to reproduce: 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer 2. EXEC: Right click on project -> New -> Resource... 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) 4. EXEC: hit Finish 5. Error message is not shown correctly and it shows stacktrace(see screenshot). was: Steps to reproduce: 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer 2. EXEC: Right click on project -> New -> Resource... 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) 4. EXEC: hit Finish 5. Error message is not shown correctly and it shows stacktrace: > Improve error message when resource does not exist > -------------------------------------------------- > > Key: JBIDE-25697 > URL: https://issues.jboss.org/browse/JBIDE-25697 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM1 > Reporter: Josef Kopriva > Attachments: Screenshot_20180209_104512.png > > > Steps to reproduce: > 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer > 2. EXEC: Right click on project -> New -> Resource... > 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) > 4. EXEC: hit Finish > 5. Error message is not shown correctly and it shows stacktrace(see screenshot). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25697) Improve error message when resource does not exist

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-25697: ------------------------------------- Summary: Improve error message when resource does not exist Key: JBIDE-25697 URL: https://issues.jboss.org/browse/JBIDE-25697 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.3.AM1 Reporter: Josef Kopriva Steps to reproduce: 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer 2. EXEC: Right click on project -> New -> Resource... 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) 4. EXEC: hit Finish 5. Error message is not shown correctly and it shows stacktrace: -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25166) Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25166?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25166. --------------------------------- Closing. No error is shown in ErrorLog. Verified in: Red Hat JBoss Developer Studio Version: 11.3.0.AM1 Build id: AM1-v20180209-0708-B2024 Build date: 20180209-0708 > Resource wizard: using (formally valid) URL to non-existing/erroneous json does not show error message > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-25166 > URL: https://issues.jboss.org/browse/JBIDE-25166 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Labels: openshift_v3, resource_wizard > Fix For: 4.5.3.AM1 > > Attachments: image-2017-10-27-15-12-22-841.png, valid-url-no-errors.png > > > Steps to reproduce: > 1. ASSERT: Have project in OpenShift connection in OpenShift Explorer > 2. EXEC: Right click on project -> New -> Resource... > 3. EXEC: Enter URL to non-existing template/json (ex. https://raw.githubusercontent.com/jbosstools/jbosstools-openshift/master/...) > 4. EXEC: hit Finish > Result: > no error is shown -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25602) NullPointerException in RegistryProviderModel.getRegistryURL

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25602?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25602. --------------------------------- Closing. PR is merged. Cannot reproduce - no steps. AERI record is updated. > NullPointerException in RegistryProviderModel.getRegistryURL > ------------------------------------------------------------ > > Key: JBIDE-25602 > URL: https://issues.jboss.org/browse/JBIDE-25602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Automated Error Reporting Bot > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > The following problem was reported via the automated error reporting: > Message: Unhandled event loop exception > {noformat} > java.lang.NullPointerException: null > at org.jboss.tools.openshift.core.connection.registry.RegistryProviderModel.getRegistryURL(RegistryProviderModel.java:37) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.discoverRegistryPressed(AdvancedConnectionEditor.java:302) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor.access$2(AdvancedConnectionEditor.java:300) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$1$1.widgetSelected(AdvancedConnectionEditor.java:128) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > {noformat} > Bundles: > | org.eclipse.swt | 3.106.0.v20170608-0516 | 3.106.1.v20170926-0519 | > | org.jboss.tools.openshift.core | 3.4.1.v20171025-1008 | 3.4.2.v20171115-1821 | > | org.jboss.tools.openshift.ui | 3.4.1.v20171025-1219 | 3.4.2.v20171115-1650 | > Operating Systems: > | Linux | 4.10.0 | 4.10.0 | > | MacOSX | 10.13.1 | 10.13.2 | > | Windows | 6.2.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/5a2a4339e4b037...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25614) Upgrade embedded Jolokia client to 1.4.0

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25614?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25614. --------------------------------- Closing, PRs are merged. Verified in: Red Hat JBoss Developer Studio Version: 11.3.0.AM1 Build id: AM1-v20180209-0708-B2024 Build date: 20180209-0708 > Upgrade embedded Jolokia client to 1.4.0 > ---------------------------------------- > > Key: JBIDE-25614 > URL: https://issues.jboss.org/browse/JBIDE-25614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.5.3.AM1 > > > a new version of Jolokia is available. > Would be nice to leverage it. > Need to check that it is backward -compatible (but seems so at first-sight based on release notes) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4670) For JBDS 11.3.0.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [installer]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4670?page=com.atlassian.jira.plugin.... ] Jeff MAURY closed JBDS-4670. ---------------------------- Resolution: Done > For JBDS 11.3.0.AM1: Prepare for 4.5.3.AM1 / 11.3.0.AM1 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4670 > URL: https://issues.jboss.org/browse/JBDS-4670 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.3.0.AM1 > > > For JBDS 11.3.0.AM1 [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.3.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.3.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.71.1.Final > > {code} > mvn clean verify -Dtpc.version=4.71.1.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.72.0.Final > > {code} > mvn clean verify -Dtpc.version=4.72.0.Final > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-884) Add a scenario description to each SY test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-884?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-884. ----------------------------------- Resolution: Won't Do SwitchYard tooling is now deprecated and will be removed in Devstudio 12.x > Add a scenario description to each SY test > ------------------------------------------ > > Key: JBTIS-884 > URL: https://issues.jboss.org/browse/JBTIS-884 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > Just use the JavaDoc as it is used in Fuse tests -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-833) Extend transformers tests by the new attribute in JAXB transformer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-833?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-833. ----------------------------------- Resolution: Won't Do SwitchYard tooling is now deprecated and will be removed in Devstudio 12.x > Extend transformers tests by the new attribute in JAXB transformer > ------------------------------------------------------------------ > > Key: JBTIS-833 > URL: https://issues.jboss.org/browse/JBTIS-833 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, switchyard > Affects Versions: 4.3.1.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Attachments: switchyard-example.zip > > > See SWITCHYARD-2923 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-619) Extend scaReferenceBindingTest by preferLocal and its default behavior

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-619?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-619. ----------------------------------- Resolution: Won't Do SwitchYard tooling is now deprecated and will be removed in Devstudio 12.x > Extend scaReferenceBindingTest by preferLocal and its default behavior > ---------------------------------------------------------------------- > > Key: JBTIS-619 > URL: https://issues.jboss.org/browse/JBTIS-619 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.3.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > SCA reference binding shows the attribute 'preferLocal' as 'true' but the result xml doesn't include this value (and its default value is false). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018