December 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24111) Verify EAP 7.1 compatibility from EAP team

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24111?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24111: ------------------------------------- EAP 7.1 final has following jars: jboss-dmr-1.4.1.Final-redhat-1.jar jboss-logging-3.3.1.Final-redhat-1.jar jboss-remoting-5.0.5.Final-redhat-1.jar jboss-threads-2.2.1.Final-redhat-1.jar wildfly-client-config-1.0.0.Final-redhat-1.jar wildfly-common-1.2.0.Final-redhat-1.jar wildfly-controller-client-3.0.10.Final-redhat-1.jar wildfly-elytron-integration-3.0.10.Final-redhat-1.jar wildfly-elytron-1.1.7.Final-redhat-1.jar wildfly-protocol-3.0.10.Final-redhat-1.jar xnio-api-3.5.4.Final-redhat-1.jar xnio-nio-3.5.4.Final-redhat-1.jar This is different than current bundled libs: - wildfly-controller-client-3.0.8.Final.jar - wildfly-elytron-1.1.6.Final.jar - wildfly-protocol-3.0.8.Final.jar + wildfly-controller-client-3.0.10.Final.jar + wildfly-elytron-1.1.7.Final.jar + wildfly-protocol-3.0.10.Final.jar Since these are all micro changes, it should be fine whether we update or don't update. > Verify EAP 7.1 compatibility from EAP team > ------------------------------------------ > > Key: JBIDE-24111 > URL: https://issues.jboss.org/browse/JBIDE-24111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: eap, server > Fix For: 4.5.x > > > We should check the problems got from the EAP team. See linked issues -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24111) Verify EAP 7.1 compatibility from EAP team

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24111?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24111: ------------------------------- Sprint: devex #131 April 2017, devex #138 September 2017, devex #142 December 2017 (was: devex #131 April 2017, devex #138 September 2017) > Verify EAP 7.1 compatibility from EAP team > ------------------------------------------ > > Key: JBIDE-24111 > URL: https://issues.jboss.org/browse/JBIDE-24111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.4.AM1 > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: eap, server > Fix For: 4.5.x > > > We should check the problems got from the EAP team. See linked issues -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25261) Edit button is enabled for non existing credentials

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25261?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25261: ------------------------------- Sprint: devex #142 December 2017 > Edit button is enabled for non existing credentials > --------------------------------------------------- > > Key: JBIDE-25261 > URL: https://issues.jboss.org/browse/JBIDE-25261 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.5.1.Final > Reporter: Josef Kopriva > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.5.x > > Attachments: image-2017-10-17-10-46-28-389.png, image-2017-10-17-10-47-26-446.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25260) Console view is broken after entering subscription username

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25260?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25260: ------------------------------- Sprint: devex #142 December 2017 > Console view is broken after entering subscription username > ----------------------------------------------------------- > > Key: JBIDE-25260 > URL: https://issues.jboss.org/browse/JBIDE-25260 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.5.1.Final > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.5.x > > Attachments: image-2017-10-17-10-38-53-270.png, with_devstudio_11.0.0.GA-0.PNG, with_devstudio_11.0.0.GA-1.PNG > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4638) Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4638?page=com.atlassian.jira.plugin.... ] Vojtech Prusa commented on JBDS-4638: ------------------------------------- Working on https://github.com/vprusa/jbosstools-integration-tests/tree/JBDS-4638 (locally passed) once https://github.com/jbosstools/jbosstools-integration-tests/pull/1903 is merged > Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11 > ---------------------------------------------------------------------------- > > Key: JBDS-4638 > URL: https://issues.jboss.org/browse/JBDS-4638 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Server: WF11 > Quickstart: 11.x > Reporter: Vojtech Prusa > Attachments: jts.errors.txt > > > Automation fails because of error (manually tested in attachment) for this quickstart. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > and > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I suppose this error is duplicate to: > https://bugzilla.redhat.com/show_bug.cgi?id=1192591 > Using mentioned workaround I get: > Description Resource Path Location Type > Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > What I did to get rid of this error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" > thought i think this is wrong approach and i did not deploy this quickstart yet. > Please make a comment > [~wolfc] [~rob.stryker] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4638) Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4638?page=com.atlassian.jira.plugin.... ] Vojtech Prusa updated JBDS-4638: -------------------------------- Description: Automation fails because of error (manually tested in attachment) for this quickstart. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... and https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... I suppose this error is duplicate to: https://bugzilla.redhat.com/show_bug.cgi?id=1192591 Using mentioned workaround I get: Description Resource Path Location Type Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem What I did to get rid of this error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" thought i think this is wrong approach and i did not deploy this quickstart yet. Please make a comment [~wolfc] [~rob.stryker] [~sgilda] Thank you. was: Automation fails because of error (manually tested in attachment) for this quickstart. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... and https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... I suppose this error is duplicate to: https://bugzilla.redhat.com/show_bug.cgi?id=1192591 Using mentioned workaround I get: Description Resource Path Location Type Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem What did get rid of the error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" thought i think this is wrong approach and i did not deploy this quickstart yet. Please make a comment [~wolfc] [~rob.stryker] [~sgilda] Thank you. > Failing tests for quickstarts [jts][ejb-security-interceptors] on WildFly-11 > ---------------------------------------------------------------------------- > > Key: JBDS-4638 > URL: https://issues.jboss.org/browse/JBDS-4638 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Server: WF11 > Quickstart: 11.x > Reporter: Vojtech Prusa > Attachments: jts.errors.txt > > > Automation fails because of error (manually tested in attachment) for this quickstart. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > and > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I suppose this error is duplicate to: > https://bugzilla.redhat.com/show_bug.cgi?id=1192591 > Using mentioned workaround I get: > Description Resource Path Location Type > Referenced file contains errors (jar:file:~/ws/devstudio-11.2.0.AM2-v20171210-2039-B1746/studio/plugins/org.jboss.tools.as.catalog_3.5.2.v20171114-2016.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > What I did to get rid of this error message was removing from xsi:schemaLocation string "http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd" > thought i think this is wrong approach and i did not deploy this quickstart yet. > Please make a comment > [~wolfc] [~rob.stryker] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4636) Failing tests for quickstart [spring-petclinic] on WildFly-11

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on JBDS-4636: ----------------------------------- I don't mind dropping spring-petclinic QS from EAP Quick starts As [~trepel] says it is quite outdated and we do not keep it in line with upstream version. It might be worth looking into providing some other guideline how to deploy petclinic on EAP in context of OpenShift so we still have the added value on how to deploy it, but shipping it as part of our product quickstarts is probably not needed anymore. > Failing tests for quickstart [spring-petclinic] on WildFly-11 > ------------------------------------------------------------- > > Key: JBDS-4636 > URL: https://issues.jboss.org/browse/JBDS-4636 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: jdk=jdk1.8,label=fedora26 > jdk=jdk1.8,label=ubuntu1704 > jdk=openjdk-1.8,label=fedora26 > jdk=openjdk-1.8,label=win10 > Server: WF11 > Quickstarts: 11.x > Reporter: Vojtech Prusa > Attachments: spring-petclinic.errors.txt > > > There are JavaScript related errors in JBDS for which automation fails. > Related test reports: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Test results: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > I think there may be some other configuration for JavaScript support necessary. > I was successful at deploying this quickstart. > Errors bothering me most are: > ')' expected intro.js /spring-petclinic/src/main/webapp/vendors/jquery/src line 20 > and > The element type "meta" must be terminated by the matching end-tag "</meta>". > I have added Spring IDE plugin to JBDS but I still get same errors. > Please comment [~n1hility] [~ctomc] [~trepel] [~sgilda] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1195) invalid children in composite sites listed on ide-config.properties

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1195?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBTIS-1195. ------------------------------------ Verified, now we have a green job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > invalid children in composite sites listed on ide-config.properties > ------------------------------------------------------------------- > > Key: JBTIS-1195 > URL: https://issues.jboss.org/browse/JBTIS-1195 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: build, releng > Affects Versions: 4.5.1.Beta1b > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.5.1.CR1 > > > I recently wrote a URL checker [1] for ide-config.properties to see if all the linked sites are valid. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Turns out... we have some 404s in there. > {code}23:15:43 [INFO] Checking for valid children in: http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... > 23:15:45 {24/45} [3/3] > > http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... : NOT FOUND > > 23:17:39 [INFO] Checking for valid children in: https://devstudio.redhat.com/updates/8.0/integration-stack/extras//compos... > 23:17:44 {45/45} [3/3] > > https://devstudio.redhat.com/updates/8.0/integration-stack/extras//jboss-... : NOT FOUND{code} > Both of these seem to be caused by the fact that there are update sites (which are NOT composites) but which have compositeContent.xml files in them. > 1. http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... should not exist, since http://download.jboss.org/jbosstools/updates/stable/luna/integration-stac... has its own content.jar and artifacts.jar > 2. https://devstudio.redhat.com/updates/8.0/integration-stack/extras//jboss-... should not esxit, since https://devstudio.redhat.com/updates/8.0/integration-stack/extras//jboss-... has its own content.jar and artifacts.jar -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4637) Failing quickstart WildFly-11 [template]

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBDS-4637?page=com.atlassian.jira.plugin.... ] Josef Kopriva commented on JBDS-4637: ------------------------------------- [~vprusa] we can exclude it :) > Failing quickstart WildFly-11 [template] > ---------------------------------------- > > Key: JBDS-4637 > URL: https://issues.jboss.org/browse/JBDS-4637 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > WF11 > quickstartes 11.0.0.Final > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: pom.xml > > > Automation fails because of error after template project is imported. > Test report: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Solutions: > https://stackoverflow.com/questions/31835033/web-xml-is-missing-and-failo... > Updated pom.xml as attachment does no show errors after Project Maven -> Update project .. > Idk if right solution is to change pom or generate web.xml with "Java EE Tools -> Generate Deployment Descriptor Stub" in test. > Please comment recommendations [~n1hility] [~ctomc] [~trepel] [~sgilda] [~jkopriva] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4637) Failing quickstart WildFly-11 [template]

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBDS-4637?page=com.atlassian.jira.plugin.... ] Vojtech Prusa commented on JBDS-4637: ------------------------------------- [~ ctomc] Because the integration tests download the entire repo as zip and then import each folder / quickstart as Maven -> Import -> Existing project, this process does not distinguish if it should be buildable just verifies that the project is importable and imported without errors. So I suggest exclude "template" from integration tests, because if valid errors would occur, errors in "template" would be duplicates. What do you think [jkopriva]? > Failing quickstart WildFly-11 [template] > ---------------------------------------- > > Key: JBDS-4637 > URL: https://issues.jboss.org/browse/JBDS-4637 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: project-examples > Affects Versions: 11.2.0.AM2 > Environment: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > WF11 > quickstartes 11.0.0.Final > Reporter: Vojtech Prusa > Assignee: Vojtech Prusa > Attachments: pom.xml > > > Automation fails because of error after template project is imported. > Test report: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/examples... > Solutions: > https://stackoverflow.com/questions/31835033/web-xml-is-missing-and-failo... > Updated pom.xml as attachment does no show errors after Project Maven -> Update project .. > Idk if right solution is to change pom or generate web.xml with "Java EE Tools -> Generate Deployment Descriptor Stub" in test. > Please comment recommendations [~n1hility] [~ctomc] [~trepel] [~sgilda] [~jkopriva] > Thank you. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 December 2017