April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24208) Arquillian New and Noteworthy for 4.4.4.AM3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24208?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-24208. --------------------------------- > Arquillian New and Noteworthy for 4.4.4.AM3 > --------------------------------------------------- > > Key: JBIDE-24208 > URL: https://issues.jboss.org/browse/JBIDE-24208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > > Snjezana Peco, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24190 #comment Create N&N for Arquillian 4.4.4.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24208) Arquillian New and Noteworthy for 4.4.4.AM3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24208?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-24208. ----------------------------------- Resolution: Rejected No changes for N&N. > Arquillian New and Noteworthy for 4.4.4.AM3 > --------------------------------------------------- > > Key: JBIDE-24208 > URL: https://issues.jboss.org/browse/JBIDE-24208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Jeff MAURY > Assignee: Snjezana Peco > Priority: Critical > > Snjezana Peco, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Arquillian JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Arquillian, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Arquillian by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24190 #comment Create N&N for Arquillian 4.4.4.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Arquillian for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1069) Missing org.jboss.tools.ws.feature in JBTIS-TP

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1069?page=com.atlassian.jira.plugin... ] Paul Leacu closed JBTIS-1069. ----------------------------- Resolution: Rejected Eliminated on purpose for efficiency - let me know if you still need it. > Missing org.jboss.tools.ws.feature in JBTIS-TP > ---------------------------------------------- > > Key: JBTIS-1069 > URL: https://issues.jboss.org/browse/JBTIS-1069 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.2.Final-TP > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > I noticed that the feature > {code} > org.jboss.tools.ws.feature > {code} > was removed in 4.4.2.Final-TP but it was available in 4.4.1.Final-TP. Is there any reason for that? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24141) Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24141?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24141: ------------------------------------ Second test appears intermittently failing as it's now 6 builds later and the number of consecutive failures is only 2. There is however a NEW test failure: {code} Regression org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication Failing for the past 1 build (Since Unstable#81 ) Took 0.13 sec. add description Error Message Expected: <5> but: was <9> Stacktrace java.lang.AssertionError: Expected: <5> but: was <9> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at org.junit.Assert.assertThat(Assert.java:956) at org.junit.Assert.assertThat(Assert.java:923) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.indexation.JaxrsElementsIndexationDelegateTestCase.shouldIndexAndRetrieveMultipleEndpointsFromJavaApplication(JaxrsElementsIndexationDelegateTestCase.java:164){code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component > ------------------------------------------------------------ > > Key: JBIDE-24141 > URL: https://issues.jboss.org/browse/JBIDE-24141 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.4.4.AM2 > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for webservices component:* > https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for webservices component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication 0.15 sec 2 > {code} > {code} > Failed > org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication > Failing for the past 2 builds (Since Unstable#74 ) > Took 0.15 sec. > add description > Error Message > Expected: <6> > but: was <10> > Stacktrace > java.lang.AssertionError: > Expected: <6> > but: was <10> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.junit.Assert.assertThat(Assert.java:923) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.shouldChangeEndpointUriPathTemplateWhenSwitchingToWebxmlCoreApplication(JaxrsMetamodelChangedProcessorTestCase.java:358) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24140) Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24140?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24140: ------------------------------------ As of build 85 (6 builds later), tests still failing on Jenkins: {code} org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig 1 sec 4 org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments 0.52 sec 17 {code} Given that the *testPathsInLoginConfig* test is only at 4 consecutive failures, I'd agree it's intermittent - if it failed every time we'd see 11 failures. Maybe it should be disabled? But for the second test, *testServletClassWithIdenticalComments*, that's now 17 consecutive failures -- 6 more than for build 79. Therefore it's failing EVERY TIME and should be investigated. > Test Failure(s) in JBIDE 4.4.4.AM2 for jst component - org.jboss.tools.jst.web.test.WebXMLValidationTest > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24140 > URL: https://issues.jboss.org/browse/JBIDE-24140 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Affects Versions: 4.4.4.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.4.4.AM2 > > > *2 Test Failure(s) in JBIDE 4.4.4.AM2 for jst component:* > http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/d... > [Search for Test Failure JIRAs in JBIDE 4.4.4.AM2 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig 0.56 sec 5 > org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments 15 ms 11 > {code} > {code} > Failed > org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments (from org.jboss.tools.jst.web.test.JstWebAllTests) > Failing for the past 11 builds (Since #69 ) > Took 15 ms. > add description > Error Message > Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9 > Stacktrace > junit.framework.AssertionFailedError: Marker matches the 'servlet-class references to non-existent class "javax.faces.webapp.FacesServlet111"' pattern was found at wrong lines. Expected: 11 but were: 9 > 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.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:200) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:413) > at org.jboss.tools.tests.AbstractResourceMarkerTest.assertMarkerIsCreated(AbstractResourceMarkerTest.java:409) > at org.jboss.tools.jst.web.test.WebXMLValidationTest.testServletClassWithIdenticalComments(WebXMLValidationTest.java:55){code} > {code} > Failed > org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig (from org.jboss.tools.jst.web.test.JstWebAllTests) > Failing for the past 5 builds (Since Unstable#75 ) > Took 0.56 sec. > add description > Stacktrace > junit.framework.AssertionFailedError: null > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertTrue(Assert.java:31) > at junit.framework.TestCase.assertTrue(TestCase.java:201) > at org.jboss.tools.jst.web.test.WebXMLValidationTest.testPathsInLoginConfig(WebXMLValidationTest.java:103){code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24224) Web.xml tree view layout is overlapping

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-24224: ------------------------------------- Summary: Web.xml tree view layout is overlapping Key: JBIDE-24224 URL: https://issues.jboss.org/browse/JBIDE-24224 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.4.4.AM2 Environment: Fedora, Eclipse jee-neon (neon.3 based), JBT 4.4.4AM2 Reporter: Ondrej Dockal Priority: Minor Attachments: Screenshot_20170404_182307.png There is somehow overlapping label of Web Descriptor and some other text. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24096) OpenShift New and Noteworthy for 4.4.4.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24096?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24096. ------------------------------ Resolution: Rejected > OpenShift New and Noteworthy for 4.4.4.AM2 > --------------------------------------------------- > > Key: JBIDE-24096 > URL: https://issues.jboss.org/browse/JBIDE-24096 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.4.4.AM2 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24086 #comment Create N&N for OpenShift 4.4.4.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24195) Forge New and Noteworthy for 4.4.4.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24195?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-24195: ------------------------------------ Master is for Oxygen (4.5.0.AM1), 4.4.4 is on jbosstools-4.4.x but it's code frozen until we get a notif from [~nickboldt] > Forge New and Noteworthy for 4.4.4.AM3 > --------------------------------------------------- > > Key: JBIDE-24195 > URL: https://issues.jboss.org/browse/JBIDE-24195 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24190 #comment Create N&N for Forge 4.4.4.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1011) Create UI test for language / dataformats properties

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1011?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1011: ------------------------------ Fix Version/s: 10.3.0.CR1 (was: 10.2.0.GA) > Create UI test for language / dataformats properties > ---------------------------------------------------- > > Key: JBTIS-1011 > URL: https://issues.jboss.org/browse/JBTIS-1011 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 10.0.0.GA > Reporter: Lars Heinemann > Assignee: Andrej Podhradsky > Fix For: 10.3.0.CR1 > > > If you select a "transform" endpoint in the diagram and set a new expression language the pom.xml should be updated to contain the dependency of the new language if not yet there. > Same applies to dataformats (for instance "marshal" endpoints). Whenever you change the dataformat in the properties view to some other data format the dependency for that data format should be added to the pom.xml if its not yet there. > Please find more information on this issue in FUSETOOLS-2186. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4318) Detect Hyper-V version

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4318?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4318: -------------------------------- Labels: Sprint_Demo (was: ) > Detect Hyper-V version > ---------------------- > > Key: JBDS-4318 > URL: https://issues.jboss.org/browse/JBDS-4318 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.3.0.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Sudhir Verma > Labels: Sprint_Demo > Fix For: 10.4.0.AM2 > > > {code} > powershell -ExecutionPolicy ByPass -command "(get-item c:\\windows\\system32\\vmms.exe).VersionInfo.ProductVersion" > {code} > The output would be the version -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 2017