December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23644) Go to Selection is not working correctly

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23644?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-23644: ------------------------------------- Assignee: George Gastaldi > Go to Selection is not working correctly > ---------------------------------------- > > Key: JBIDE-23644 > URL: https://issues.jboss.org/browse/JBIDE-23644 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.3.AM1 > Environment: Fedora 25 + KDE > Red Hat JBoss Developer Studio > Version: 10.3.0.AM1 > Build id: AM1-v20161212-1159-B6656 > Build date: 20161212-1159 > Reporter: Josef Kopriva > Assignee: George Gastaldi > > Go to Selection is not always working. When user is switching between classes quite quickly, then user is not switched to selected class. If user is switching between classes slowly, then it works correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23644) Go to Selection is not working correctly

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-23644: ------------------------------------- Summary: Go to Selection is not working correctly Key: JBIDE-23644 URL: https://issues.jboss.org/browse/JBIDE-23644 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.4.3.AM1 Environment: Fedora 25 + KDE Red Hat JBoss Developer Studio Version: 10.3.0.AM1 Build id: AM1-v20161212-1159-B6656 Build date: 20161212-1159 Reporter: Josef Kopriva Go to Selection is not always working. When user is switching between classes quite quickly, then user is not switched to selected class. If user is switching between classes slowly, then it works correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7958) TestNG tests fail in Seam project + AS6

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7958?page=com.atlassian.jira.plugin... ] Marek Novotny commented on JBIDE-7958: -------------------------------------- I would close this issue as outdated. Seam 2.2.x won't work with JSF2 - in test or real container. If you would like to use JSF2 - use Seam 2.3.x. > TestNG tests fail in Seam project + AS6 > --------------------------------------- > > Key: JBIDE-7958 > URL: https://issues.jboss.org/browse/JBIDE-7958 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 3.2.0.Beta2 > Environment: JDK 1.6_23 > Linux x86_64 > Seam 2.2.1.CR3 > Reporter: Jozef Hartinger > Assignee: Jeff MAURY > Fix For: LATER > > > Steps to reproduce: > 1.) Create new seam web project (EAR) > 2.) Create new seam action (using new action wizard) > 3.) Run the generated test (i.e. HelloTest.java) as a TestNG test. > 4.) Add the following VM argument to the test run configuration -Dsun.lang.ClassLoader.allowArraySyntax=true > 5.) Run the test again > The test fails with the following stacktrace: > FAILED: test_hello > java.lang.AssertionError: java.lang.UnsupportedOperationException > at org.jboss.seam.mock.AbstractSeamTest$Request.onException(AbstractSeamTest.java:463) > at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:512) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) > at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) > at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) > at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) > at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) > at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) > at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) > at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) > at org.jboss.seam.mock.AbstractSeamTest$Request.run(AbstractSeamTest.java:499) > at org.domain.jbtoolsear.test.HelloTest.test_hello(HelloTest.java:26) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:74) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:673) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:846) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1168) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) > at org.testng.TestRunner.runWorkers(TestRunner.java:1125) > at org.testng.TestRunner.privateRun(TestRunner.java:749) > at org.testng.TestRunner.run(TestRunner.java:600) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:317) > at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312) > at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274) > at org.testng.SuiteRunner.run(SuiteRunner.java:223) > at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) > at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) > at org.testng.TestNG.runSuitesSequentially(TestNG.java:954) > at org.testng.TestNG.runSuitesLocally(TestNG.java:883) > at org.testng.TestNG.run(TestNG.java:817) > at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:110) > at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:205) > at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:174) > Caused by: java.lang.UnsupportedOperationException > at javax.faces.context.FacesContext.getAttributes(FacesContext.java:137) > at javax.faces.component.UIViewRoot.setViewId(UIViewRoot.java:325) > at org.jboss.seam.mock.MockViewHandler.createView(MockViewHandler.java:28) > at org.jboss.seam.jsf.SeamViewHandler.createView(SeamViewHandler.java:68) > at org.jboss.seam.mock.AbstractSeamTest$Request.restoreViewPhase(AbstractSeamTest.java:734) > at org.jboss.seam.mock.AbstractSeamTest$Request.emulateJsfLifecycle(AbstractSeamTest.java:591) > at org.jboss.seam.mock.AbstractSeamTest$Request.access$100(AbstractSeamTest.java:177) > at org.jboss.seam.mock.AbstractSeamTest$Request$2.doFilter(AbstractSeamTest.java:505) > ... 45 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23640) Integration tests: Once PushImageTest starts to fail, it will always fail if no image cleanup happens in the test suite

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23640?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-23640: --------------------------------------- [~adietish] Reviewed, please fix, otherwise it looks good. > Integration tests: Once PushImageTest starts to fail, it will always fail if no image cleanup happens in the test suite > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23640 > URL: https://issues.jboss.org/browse/JBIDE-23640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > > PushImageTest is add a tag to an image. When looking at the images, it is comparing all of the decoration with the tag. This works fine as long as the image only has 1 tag, once it gets more, the lookup for the image starts to fail. The image is deleted later in the test, so if the image with the tag is not found, the delete wont happen and subsequent lookups will fail. This most likely wont happen if you run the complete suite because the suite is cleaning up, but it will happen if you run a single test. > Another problem is that PushImageTest wont wait until the freshly tagged image was successfully pushed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4046) Test Quick Starts (EAP 7.1) with devstudio

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4046?page=com.atlassian.jira.plugin.... ] Josef Kopriva updated JBDS-4046: -------------------------------- Component/s: project-examples > Test Quick Starts (EAP 7.1) with devstudio > ------------------------------------------- > > Key: JBDS-4046 > URL: https://issues.jboss.org/browse/JBDS-4046 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: central, project-examples, runtime > Reporter: Alexey Kazakov > Assignee: Josef Kopriva > Fix For: 10.3.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4046) Test Quick Starts (EAP 7.1) with devstudio

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4046?page=com.atlassian.jira.plugin.... ] Josef Kopriva closed JBDS-4046. ------------------------------- Closing, quickstarts are tested. > Test Quick Starts (EAP 7.1) with devstudio > ------------------------------------------- > > Key: JBDS-4046 > URL: https://issues.jboss.org/browse/JBDS-4046 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: central, project-examples, runtime > Reporter: Alexey Kazakov > Assignee: Josef Kopriva > Fix For: 10.3.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4046) Test Quick Starts (EAP 7.1) with devstudio

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4046?page=com.atlassian.jira.plugin.... ] Josef Kopriva resolved JBDS-4046. --------------------------------- Resolution: Done > Test Quick Starts (EAP 7.1) with devstudio > ------------------------------------------- > > Key: JBDS-4046 > URL: https://issues.jboss.org/browse/JBDS-4046 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: central, runtime > Reporter: Alexey Kazakov > Assignee: Josef Kopriva > Fix For: 10.3.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23641: ------------------------------------ Which version of STS ? And is this specific to MacOS Sierra ? > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: fede pia > Priority: Blocker > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23641) Jboss AS Eclipse plugin freezes STS on Mac OS Sierra

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23641?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23641: ------------------------------- Component/s: upstream > Jboss AS Eclipse plugin freezes STS on Mac OS Sierra > ---------------------------------------------------- > > Key: JBIDE-23641 > URL: https://issues.jboss.org/browse/JBIDE-23641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Reporter: fede pia > Priority: Blocker > Attachments: eclipse.log > > > When installing Jboss Tool 4.4.2 (only Jboss AS plugin) in Spring Tool Suite in a Mac, the Eclipse hangs up and needs to be killed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4220) Integration Stack Installation Guide peer review

by Gemma Sheldon (JIRA)

[ https://issues.jboss.org/browse/JBDS-4220?page=com.atlassian.jira.plugin.... ] Gemma Sheldon updated JBDS-4220: -------------------------------- Component/s: documentation Description: General peer review stuff from the JBDIS Installation Guide. *Chapter 2:* - Oxford comma after "architecture" in the first para. *Chapter 4:* - "At the Select Additional Features to Install screen, select the required components: " This could be "Select the required components from the Select Additional Features to Install screen"? - "When done, JBoss Developer Studio Integration Stack and the integration stack components are ready to use. " When complete? Once installed? - In Warning "The IDE changes do not take effect until the IDE is restarted and the IDE may be unstable until it is restarted. " Kind of awkward as IDE is repeated x3 and restarted is there twice. Maybe: The IDE changes are not applied until it is restarted. The IDE may be unstable until it is restarted and the changes take effect. *Chapter 6* - The sub-steps here could use a full stop based on the IBM style guide pp84-85. - Same Warning as in previous chapter *Chapter 7* - Same point about the sub-steps and full stops. Some have them here, some don't. - Before the last Important is missing a full stop. "For plug-in specific configuration information, see the appropriate Red Hat JBoss product documentation available from the Red Hat Customer Portal" *Chapter 8* - Several steps throughout the procedure are missing full stops at the end. - Step 2 "optional" should probably be capitalized. I'm not 100% sure of this, but it seems awkward being lower case at the beginning of a step. - Same as above with Step 6, which is also missing the opening bracket. - Same Warning as in Chapters 5 and 6. - "Click Yes to restart immediately and No if you need to save any unsaved changes to open projects. " I think using saved and unsaved together here is awkward. I would just say "If you need to save any changes to open projects." This statement also appears in Chapter 6. *Chapter 9* - "Removing one or more plug-ins that are no longer required provides continued stability and ensures continued optimal performance due to a smaller memory footprint." 2x continued here. Could be "... provides continued stability and ensures optimal performance..." - " in an efficient manner" --> efficiently. - full stops at the end of the bullet points. - substeps of step 4 are missing full stops. was: General peer review stuff from the JBDIS Installation Guide. *Chapter 2:* - Oxford comma after "architecture" in the first para. *Chapter 4:* - "At the Select Additional Features to Install screen, select the required components: " This could be "Select the required components from the Select Additional Features to Install screen"? - "When done, JBoss Developer Studio Integration Stack and the integration stack components are ready to use. " When complete? Once installed? - In Warning "The IDE changes do not take effect until the IDE is restarted and the IDE may be unstable until it is restarted. " Kind of awkward as IDE is repeated x3 and restarted is there twice. Maybe: The IDE changes are not applied until it is restarted. The IDE may be unstable until it is restarted and the changes take effect. *Chapter 6* - The sub-steps here could use a full stop based on the IBM style guide pp84-85. - Same Warning as in previous chapter *Chapter 7* - Same point about the sub-steps and full stops. Some have them here, some don't. - Before the last Important is missing a full stop. "For plug-in specific configuration information, see the appropriate Red Hat JBoss product documentation available from the Red Hat Customer Portal" *Chapter 8* - Several steps throughout the procedure are missing full stops at the end. - Step 2 "optional" should probably be capitalized. I'm not 100% sure of this, but it seems awkward being lower case at the beginning of a step. - Same as above with Step 6, which is also missing the opening bracket. - Same Warning as in Chapters 5 and 6. Affects: Documentation (Ref Guide, User Guide, etc.) Writer: Misha Ali > Integration Stack Installation Guide peer review > ------------------------------------------------ > > Key: JBDS-4220 > URL: https://issues.jboss.org/browse/JBDS-4220 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: documentation, integration-platform > Reporter: Gemma Sheldon > Priority: Minor > > General peer review stuff from the JBDIS Installation Guide. > *Chapter 2:* > - Oxford comma after "architecture" in the first para. > *Chapter 4:* > - "At the Select Additional Features to Install screen, select the required components: " > This could be "Select the required components from the Select Additional Features to Install screen"? > - "When done, JBoss Developer Studio Integration Stack and the integration stack components are ready to use. " > When complete? Once installed? > - In Warning "The IDE changes do not take effect until the IDE is restarted and the IDE may be unstable until it is restarted. " > Kind of awkward as IDE is repeated x3 and restarted is there twice. Maybe: > The IDE changes are not applied until it is restarted. The IDE may be unstable until it is restarted and the changes take effect. > *Chapter 6* > - The sub-steps here could use a full stop based on the IBM style guide pp84-85. > - Same Warning as in previous chapter > *Chapter 7* > - Same point about the sub-steps and full stops. Some have them here, some don't. > - Before the last Important is missing a full stop. "For plug-in specific configuration information, see the appropriate Red Hat JBoss product documentation available from the Red Hat Customer Portal" > *Chapter 8* > - Several steps throughout the procedure are missing full stops at the end. > - Step 2 "optional" should probably be capitalized. I'm not 100% sure of this, but it seems awkward being lower case at the beginning of a step. > - Same as above with Step 6, which is also missing the opening bracket. > - Same Warning as in Chapters 5 and 6. > - "Click Yes to restart immediately and No if you need to save any unsaved changes to open projects. " I think using saved and unsaved together here is awkward. I would just say "If you need to save any changes to open projects." > This statement also appears in Chapter 6. > *Chapter 9* > - "Removing one or more plug-ins that are no longer required provides continued stability and ensures continued optimal performance due to a smaller memory footprint." > 2x continued here. Could be "... provides continued stability and ensures optimal performance..." > - " in an efficient manner" --> efficiently. > - full stops at the end of the bullet points. > - substeps of step 4 are missing full stops. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 December 2016