January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21570) Fix ECMA5 content assist JUnit test

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21570?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-21570: -------------------------------- Fix Version/s: (was: 4.3.1.Beta2) > Fix ECMA5 content assist JUnit test > ----------------------------------- > > Key: JBIDE-21570 > URL: https://issues.jboss.org/browse/JBIDE-21570 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript > Affects Versions: 4.3.1.Beta1 > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 4.4.0.Alpha1 > > > During CI build on jenkins JUnit I test fails. Filing test checks for ECMA5 related proposals in content assist for .js file in JavaScript project. With manually created project and .js file everything works as expected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21297?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-21297. ------------------------------- Verified on Jenkins > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component > -------------------------------------------------------------------- > > Key: JBIDE-21297 > URL: https://issues.jboss.org/browse/JBIDE-21297 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: testfailure > Fix For: 4.3.1.Beta2 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m... > # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5} > <case> > <age>8</age> > <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className> > <duration>1.777</duration> > <errorDetails>Content Assistant returned no proposals</errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61) > </errorStackTrace> > <failedSince>61</failedSince> > <name>testJstJsdtTernCAOnEcma5</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21569) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-21569: ----------------------------------- Summary: 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component Key: JBIDE-21569 URL: https://issues.jboss.org/browse/JBIDE-21569 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core Affects Versions: 4.3.1.Beta1 Reporter: Nick Boldt Assignee: Victor Rubezhny Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:* https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m... # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds) [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] ----- * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds) {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5} <case> <age>8</age> <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className> <duration>1.777</duration> <errorDetails>Content Assistant returned no proposals</errorDetails> <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.assertTrue(Assert.java:22) at junit.framework.TestCase.assertTrue(TestCase.java:192) at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79) at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61) </errorStackTrace> <failedSince>61</failedSince> <name>testJstJsdtTernCAOnEcma5</name> <skipped>false</skipped> <status>FAILED</status> </case> {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21569) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21569?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-21569: -------------------------------- Fix Version/s: (was: 4.3.1.Beta2) > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component > -------------------------------------------------------------------- > > Key: JBIDE-21569 > URL: https://issues.jboss.org/browse/JBIDE-21569 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: testfailure > Fix For: 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m... > # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5} > <case> > <age>8</age> > <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className> > <duration>1.777</duration> > <errorDetails>Content Assistant returned no proposals</errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61) > </errorStackTrace> > <failedSince>61</failedSince> > <name>testJstJsdtTernCAOnEcma5</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21569) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21569?page=com.atlassian.jira.plugi... ] Vlado Pakan resolved JBIDE-21569. --------------------------------- Resolution: Done > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component > -------------------------------------------------------------------- > > Key: JBIDE-21569 > URL: https://issues.jboss.org/browse/JBIDE-21569 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: testfailure > Fix For: 4.4.0.Alpha1 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m... > # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5} > <case> > <age>8</age> > <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className> > <duration>1.777</duration> > <errorDetails>Content Assistant returned no proposals</errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61) > </errorStackTrace> > <failedSince>61</failedSince> > <name>testJstJsdtTernCAOnEcma5</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21297) 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21297?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-21297: -------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > 1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component > -------------------------------------------------------------------- > > Key: JBIDE-21297 > URL: https://issues.jboss.org/browse/JBIDE-21297 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: testfailure > Fix For: 4.3.1.Beta2 > > > *1 Test Failure(s) in JBIDE 4.3.1.Beta1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.m... > # [org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest|https://jenkins.mw.lab.en...] (failing for 8 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.1.Beta1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest : testJstJsdtTernCAOnEcma5{color} (failing for 8 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jst_4.3.mars/68/testReport/org.jboss.tools.jst.jsdt.test/JstJsdtTernCATest/testJstJsdtTernCAOnEcma5} > <case> > <age>8</age> > <className>org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest</className> > <duration>1.777</duration> > <errorDetails>Content Assistant returned no proposals</errorDetails> > <errorStackTrace>junit.framework.AssertionFailedError: Content Assistant returned no proposals > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.doJstJsdtTernCATest(JstJsdtTernCATest.java:79) > at org.jboss.tools.jst.jsdt.test.JstJsdtTernCATest.testJstJsdtTernCAOnEcma5(JstJsdtTernCATest.java:61) > </errorStackTrace> > <failedSince>61</failedSince> > <name>testJstJsdtTernCAOnEcma5</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21568) No new repository found when recognizing maven repo

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21568?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-21568: ------------------------------------- Steps to Reproduce: 1. Open Configure Maven Repositories wizard -> Add Repository 2. Recognize JBoss Maven Enterprise Repositories -> Choose some repo 3. ASSERT: repo is properly recognized 4. Cancel wizard 5. repeat step 2 -> "No new repository found" will be displayed was: 1. Open Configure Maven Repositories wizard -> Add Repository 2. Recognize JBoss Maven Enterprise Repositories -> Choose some repo 3. Cancel wizard 4. repeat step 2 -> "No new repository found" will be displayed > No new repository found when recognizing maven repo > --------------------------------------------------- > > Key: JBIDE-21568 > URL: https://issues.jboss.org/browse/JBIDE-21568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.1.Beta2 > Reporter: Rastislav Wagner > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21563) [regression] Explorer: Connection or (multiple) application deletion does not work anymore

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21563: ---------------------------------- Summary: [regression] Explorer: Connection or (multiple) application deletion does not work anymore (was: [regression] Explorer: (Multiple application) deletion does not work anymore) > [regression] Explorer: Connection or (multiple) application deletion does not work anymore > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21563 > URL: https://issues.jboss.org/browse/JBIDE-21563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: explorer, openshift_v2, respin-a > Fix For: 4.3.1.Beta2, 4.3.1.CR1 > > > Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one. > Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21563) [regression] Explorer: (Multiple application) deletion does not work anymore

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21563: ---------------------------------- Priority: Critical (was: Major) > [regression] Explorer: (Multiple application) deletion does not work anymore > ---------------------------------------------------------------------------- > > Key: JBIDE-21563 > URL: https://issues.jboss.org/browse/JBIDE-21563 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Critical > Labels: explorer, openshift_v2, respin-a > Fix For: 4.3.1.Beta2, 4.3.1.CR1 > > > Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one. > Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21568) No new repository found when recognizing maven repo

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-21568: ---------------------------------------- Summary: No new repository found when recognizing maven repo Key: JBIDE-21568 URL: https://issues.jboss.org/browse/JBIDE-21568 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.3.1.Beta2 Reporter: Rastislav Wagner -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

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 January 2016