April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13939 at 4/5/13 6:37 PM: ------------------------------------------------------------------ I looked into this and I found out that GlobalUsageSettingsTest is enabling usage in the system properties while testing. The "correct" fix is therefore IMHO to ensure that this test is restoring the correct state after each test method. I implemented appropriate @Before and @After methods for this test. The tests then succeed for me (which they're not if I run then witout my fix). I suggest that we replace: https://github.com/jbosstools/jbosstools-base/pull/75 by this more "correct" fix: https://github.com/jbosstools/jbosstools-base/pull/76 was (Author: adietish): I looked into this and I found out that GlobalUsageSettingsTest is enabling usage in the system properties while testing. The "correct" fix is therefore IMHO to ensure that this test is restoring the correct state after each test method. I implemented appropriate @Before and @After methods for this test. The tests then succeed for me (which they're not if I run then witout my fix). I suggest that we apply: https://github.com/jbosstools/jbosstools-base/pull/76 and close: https://github.com/jbosstools/jbosstools-base/pull/75 > Usage tests freeze on Kepler M6 > ------------------------------- > > Key: JBIDE-13939 > URL: https://issues.jboss.org/browse/JBIDE-13939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog. > They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog. > The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest). > The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13939 at 4/5/13 6:38 PM: ------------------------------------------------------------------ I looked into this and I found out that GlobalUsageSettingsTest is enabling usage in the system properties while testing. The "correct" fix is therefore IMHO to ensure that this test is restoring the correct state after each test method. I implemented appropriate @Before and @After methods for this test. The tests then succeed for me (which they're not if I run them without my fix). I suggest that we replace: https://github.com/jbosstools/jbosstools-base/pull/75 by this more "correct" fix: https://github.com/jbosstools/jbosstools-base/pull/76 was (Author: adietish): I looked into this and I found out that GlobalUsageSettingsTest is enabling usage in the system properties while testing. The "correct" fix is therefore IMHO to ensure that this test is restoring the correct state after each test method. I implemented appropriate @Before and @After methods for this test. The tests then succeed for me (which they're not if I run then witout my fix). I suggest that we replace: https://github.com/jbosstools/jbosstools-base/pull/75 by this more "correct" fix: https://github.com/jbosstools/jbosstools-base/pull/76 > Usage tests freeze on Kepler M6 > ------------------------------- > > Key: JBIDE-13939 > URL: https://issues.jboss.org/browse/JBIDE-13939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog. > They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog. > The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest). > The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13939 at 4/5/13 6:36 PM: ------------------------------------------------------------------ I looked into this and I found out that GlobalUsageSettingsTest is enabling usage in the system properties while testing. The "correct" fix is therefore IMHO to ensure that this test is restoring the correct state after each test method. I implemented appropriate @Before and @After methods for this test. The tests then succeed for me (which they're not if I run then witout my fix). I suggest that we apply: https://github.com/jbosstools/jbosstools-base/pull/76 and close: https://github.com/jbosstools/jbosstools-base/pull/75 was (Author: adietish): I looked into this and I found out that GlobalUsageSettingsTest is enabling usage while testing. The correct fix is therefore IMHO to ensure this test is restoring the correct state after each test method. I therefore implemented appropriate @Before and @After methods for this test. The tests then succeed for me (which they're not if I run then witout my fix). https://github.com/jbosstools/jbosstools-base/pull/76 > Usage tests freeze on Kepler M6 > ------------------------------- > > Key: JBIDE-13939 > URL: https://issues.jboss.org/browse/JBIDE-13939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog. > They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog. > The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest). > The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13939: ------------------------------------------ I looked into this and I found out that GlobalUsageSettingsTest is enabling usage while testing. The correct fix is therefore IMHO to ensure this test is restoring the correct state after each test method. I therefore implemented appropriate @Before and @After methods for this test. The tests then succeed for me (which they're not if I run then witout my fix). https://github.com/jbosstools/jbosstools-base/pull/76 > Usage tests freeze on Kepler M6 > ------------------------------- > > Key: JBIDE-13939 > URL: https://issues.jboss.org/browse/JBIDE-13939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog. > They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog. > The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest). > The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13941) Marker on an unsatisfied injection point in CDI Seam config disappears after modifications

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-13941: --------------------------------------------- Summary: Marker on an unsatisfied injection point in CDI Seam config disappears after modifications Key: JBIDE-13941 URL: https://issues.jboss.org/browse/JBIDE-13941 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI extensions Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Alpha2 Test SeamConfigValidationTest.testSettingInlineBeanValuesToBeanOrSetOrMap fails when it runs after testAddClassToResolveNode. Steps: 1. Import test project CDIConfigValidationTest from plugin org.jboss.tools.cdi.seam.config.core.test. 2. Open src/META-INF/beans.xml ASSERT: Tag <s:value> in line 61 is marked 'No bean is eligible for injection to the injection point'; tag <s:Integer> in the next line is marked 'Type mismatch: cannot convert from Integer to String'. 3. Create new class org.jboss.beans.validation.test.MyBean2. ASSERT: Only marker at <v:MyBean2> in line 8 disappears ('Cannot resolve type org.jboss.beans.validation.test.MyBean2'); all other markers should persist. FAILURE: Markers 'No bean is eligible for injection...' including the one in line 61 disappear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-26) Cannot install bpel from update site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-26?page=com.atlassian.jira.plugin.s... ] Paul Leacu resolved JBTIS-26. ----------------------------- Fix Version/s: 4.0.0 Resolution: Done Thanks to Nick for catching the out-of-date repository-utils https://github.com/jbosstools/jbosstools-integration-stack/commit/6280e6f... > Cannot install bpel from update site > ------------------------------------ > > Key: JBTIS-26 > URL: https://issues.jboss.org/browse/JBTIS-26 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, releng > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.0.0 > > Attachments: bpel-error.txt > > > I'm not able to install JBoss BPEL Editor into Eclipse Juno JEE (see the attached file) from JBTIS update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > Maybe there is something wrong with the aggregation definition because I'm able to install the same BPEL editor from > http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13939) Usage tests freeze on Kepler M6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13939?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13939: ------------------------------------ Since the test involves testing UI, could it be moved to an integration-tests repo instead of the unit tests included in the usage project? > Usage tests freeze on Kepler M6 > ------------------------------- > > Key: JBIDE-13939 > URL: https://issues.jboss.org/browse/JBIDE-13939 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > > The usage tests freezes because they are executed before calling the UsageReportEnablementDialog dialog. > They set the "usage_reporting_enabled" property to true which enables opening the UsageReportEnablementDialog dialog. > The fix is to set usage_reporting_enabled=false after the latest test (UsageIntegrationTest). > The issue happens on Kepler M6. I suppose it is caused by some changes related to the handling UI messagess/jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2433) Support updating from JBDS BYOE 6 to 7 (including updating Juno to Kepler)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2433?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2433: ---------------------------------- Since this use case is no longer supported and no longer in the PRD/ERD, I renamed the job with the usual "zz_disabled_" prefix to mark it irrelevant to the current dev stream (but also make it easy to recover should we need to bring it back. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > Support updating from JBDS BYOE 6 to 7 (including updating Juno to Kepler) > -------------------------------------------------------------------------- > > Key: JBDS-2433 > URL: https://issues.jboss.org/browse/JBDS-2433 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, updatesite > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 7.0.0.Alpha2 > > > Users should be able to update from JBDS BYOE 6 in Juno to JBDS BYOE 7 in Kepler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-35) Update SwitchYard to 0.8.0.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-35?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on JBTIS-35: ---------------------------------------------- Len DiMaggio <ldimaggi(a)redhat.com> made a comment on [bug 947834|https://bugzilla.redhat.com/show_bug.cgi?id=947834] This issue is blocked by: https://issues.jboss.org/browse/JBTIS-35 A short-term workaround should be to install: http://download.jboss.org/jbosstools/updates/stable/juno/soa-tooling/swit... and http://download.eclipse.org/bpmn2-modeler/site/0.2.4/ > Update SwitchYard to 0.8.0.Final > -------------------------------- > > Key: JBTIS-35 > URL: https://issues.jboss.org/browse/JBTIS-35 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: distribution > Reporter: Rob Cernich > Assignee: Rob Cernich > Fix For: 4.0.0 > > > Also need to update BPMN2 modeler to 0.2.4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-26) Cannot install bpel from update site

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-26?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated JBTIS-26: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=947331 > Cannot install bpel from update site > ------------------------------------ > > Key: JBTIS-26 > URL: https://issues.jboss.org/browse/JBTIS-26 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, releng > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Attachments: bpel-error.txt > > > I'm not able to install JBoss BPEL Editor into Eclipse Juno JEE (see the attached file) from JBTIS update site > http://download.jboss.org/jbosstools/updates/integration/juno/integration... > Maybe there is something wrong with the aggregation definition because I'm able to install the same BPEL editor from > http://download.jboss.org/jbosstools/updates/integration/juno/integration... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 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 April 2013