December 2017 - jbosstools-issues

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

by Tomas Repel (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Tomas Repel commented on JBDS-4636: ----------------------------------- Hi [~sgilda], the git repo url: https://github.com/spring-projects/spring-petclinic You can see I did few small contributions back in 2015. The intention was to make it run on JBoss/EAP more smoothly. But since the spring-petclinic is not being maintained for some time now I can imagine our code and their code diverged a lot. I am not in EAP QE so I don't follow what was happening closely enough but were there any conclusion what quickstarts would be removed in EAP 7.2 if any? I would consider this one to be a good candidate :) > 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, 3 months

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 reassigned JBDS-4637: ----------------------------------- Assignee: Vojtech Prusa > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-25455: --------------------------------------------- btw. i just noticed the image - yeah, all of those not just buildship has nothing to do on our marketplace entry. > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-25455 at 12/19/17 6:51 PM: ----------------------------------------------------------------------- Whether something is in the JEE package has had no bearing on whether it should be on jbosstools or devstudio marketplace entries. We treat all those parts (WTP, m2e, etc.) as separate things anyways. "We'll include Buildship as a 1rst class citizen in JBT and devstudio, as we do with maven." - I don't see m2e listed as a first level feature to install. So buildship has no reason to be listed there. it should just be in the list of mirrored plugins and available from Central as something to install. was (Author: maxandersen): Whether something is in the JEE package has had no bearing on whether it should be on jbosstools or devstudio marketplace entries. We treat all those parts (WTP, m2e, etc.) as separate things anyways. "We'll include Buildship as a 1rst class citizen in JBT and devstudio, as we do with maven." - I don't see m2e listed as a first level feature to install. So buildship has no reason to be there. > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25455) JBoss Tools marketplace listing includes org.eclipse features

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25455?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-25455: --------------------------------------------- Whether something is in the JEE package has had no bearing on whether it should be on jbosstools or devstudio marketplace entries. We treat all those parts (WTP, m2e, etc.) as separate things anyways. "We'll include Buildship as a 1rst class citizen in JBT and devstudio, as we do with maven." - I don't see m2e listed as a first level feature to install. So buildship has no reason to be there. > JBoss Tools marketplace listing includes org.eclipse features > ------------------------------------------------------------- > > Key: JBIDE-25455 > URL: https://issues.jboss.org/browse/JBIDE-25455 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.5.1.Final > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > Attachments: jbosstools-eclipse-plugins-marketplace.png > > > Someone added org.eclipse.buildship and org.eclipse.wst.* features to the Marketplace listing as optional-selected features. > Shouldn't these be installed via requirements from JBT features, and therefore not needed on the site? > The list of sanctioned features in the CoreTools category on the JBT site is here: > http://download.jboss.org/jbosstools/static/oxygen/stable/updates/core/4.... > So... why did the other features get added? And if they SHOULD be there, they should also be added to the JBT site too, for consistency. Right? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18654 at 12/19/17 4:12 PM: -------------------------------------------------------------- This can now be done in Jenkins, using a toolchains.xml file, 2 new OPENJDK18 and OPENJDK19 global config variables, and either Open [11] or Oracle JDK [10] . [11] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [10] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... To use the -Pjdeps profile, need to set toolchains file too. See section "Provide Configuration files" for how to specify the toolchains file for JDK 9. Then use -Djdeps-jdk-vendor=openjdk *(default in parent pom)* or -Djdeps-jdk-vendor=oraclejdk to pick a vendor. Next, trying this with Base... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... was (Author: nickboldt): This can now be done in Jenkins, using a toolchains.xml file, 2 new OPENJDK18 and OPENJDK19 global config variables, and either Open [11] or Oracle JDK [10] . [11] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [10] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Next, trying this with Base... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > run jdeps on our jars to see how dependent we are on api that might go away in Java 9 > ------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18654: ------------------------------------ This can now be done in Jenkins, using a toolchains.xml file, 2 new OPENJDK18 and OPENJDK19 global config variables, and either Open [11] or Oracle JDK [10] . [11] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [10] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Next, trying this with Base... https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > run jdeps on our jars to see how dependent we are on api that might go away in Java 9 > ------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.5.2.Final > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) TP: update target platform & Central to Oxygen.2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-25427: ------------------------------------ central is ok for me, I'm on javaee > TP: update target platform & Central to Oxygen.2 > ------------------------------------------------ > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png, ds11.2.0.AM1-remediation.png, jbt4.5.2.AM1-remediation.png, p2diff.all.txt, p2diff.ignoreVersions.txt, p2diff.jbt.AM2.AM3.ignore.versions.txt, p2diff.jbt.AM2.AM3.latest.txt, p2diff.jbt.AM2.AM3.txt > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 or later > Also include RD 2.0.1 https://projects.eclipse.org/projects/technology.reddeer/releases/2.0.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) TP: update target platform & Central to Oxygen.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25427: ------------------------------------ TPs are still failing after TP updates in jobs and "testPR" respins. Jeff, can you review? https://github.com/jbosstools/jbosstools-javaee/pull/450 https://github.com/jbosstools/jbosstools-central/pull/415 > TP: update target platform & Central to Oxygen.2 > ------------------------------------------------ > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png, ds11.2.0.AM1-remediation.png, jbt4.5.2.AM1-remediation.png, p2diff.all.txt, p2diff.ignoreVersions.txt, p2diff.jbt.AM2.AM3.ignore.versions.txt, p2diff.jbt.AM2.AM3.latest.txt, p2diff.jbt.AM2.AM3.txt > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 or later > Also include RD 2.0.1 https://projects.eclipse.org/projects/technology.reddeer/releases/2.0.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25427) TP: update target platform & Central to Oxygen.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25427?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25427 at 12/19/17 11:57 AM: --------------------------------------------------------------- TPs are still failing after TP updates in jobs and "testPR" respins. [~jeffmaury], can you review? https://github.com/jbosstools/jbosstools-javaee/pull/450 https://github.com/jbosstools/jbosstools-central/pull/415 was (Author: nickboldt): TPs are still failing after TP updates in jobs and "testPR" respins. Jeff, can you review? https://github.com/jbosstools/jbosstools-javaee/pull/450 https://github.com/jbosstools/jbosstools-central/pull/415 > TP: update target platform & Central to Oxygen.2 > ------------------------------------------------ > > Key: JBIDE-25427 > URL: https://issues.jboss.org/browse/JBIDE-25427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.2.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > Attachments: ds11.2.0.AM1-remediation-remove-code-recommenders-Oxygen.2-install.png, ds11.2.0.AM1-remediation.png, jbt4.5.2.AM1-remediation.png, p2diff.all.txt, p2diff.ignoreVersions.txt, p2diff.jbt.AM2.AM3.ignore.versions.txt, p2diff.jbt.AM2.AM3.latest.txt, p2diff.jbt.AM2.AM3.txt > > > Switch to the latest Oxygen.2, including Jetty 9.4.7 or later > Also include RD 2.0.1 https://projects.eclipse.org/projects/technology.reddeer/releases/2.0.1 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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