December 2017 - jbosstools-issues

[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: ------------------------------------ I've added a new jdk9 profile which can be used with the jdeps one to check against jdk 9. Assuming your default JDK is 8, and you have OpenJDK 9 installed in the path below, here's how you can run a build using JDK 9: {code} export JAVA_HOME=/usr/lib/jvm/java-9/ mvn clean install -U -Pjdk9 -Pjdeps {code} > 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 updated JBIDE-18654: ------------------------------- Fix Version/s: (was: 4.3.x) > 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] (JBDS-4636) Failing quickstart [spring-petclinic] for WildFly-11

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Sande Gilda commented on JBDS-4636: ----------------------------------- I can see that `src/main/webapp/vendors/jquery/src/inro.js` is missing the ending "}". The question is whether this is because it is missing in the original Spring pet-clinic source or if we were the ones who commented out the source lines. [~trepel]: What is the URL for the original Spring source code for this project? > Failing quickstart [spring-petclinic] for 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.0.0.Final > 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 Vojtech Prusa (JIRA)

Vojtech Prusa created JBDS-4637: ----------------------------------- Summary: 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 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] (JBDS-4636) Failing quickstart [spring-petclinic] for WildFly-11

by Tomas Repel (JIRA)

[ https://issues.jboss.org/browse/JBDS-4636?page=com.atlassian.jira.plugin.... ] Tomas Repel commented on JBDS-4636: ----------------------------------- As for myself (QE for that quickstart), these errors were intentionally ignored. If you are able to ignore them as well, feel free to do it. Long story The spring-petclinic quickstart was part of WFK project. It's purpose was to demonstrate what little had to be changed to make Spring's (Pivotal's) Petclinic example work on JBoss/EAP. Only necessary changes were made so that one was able to see nice diff. The errors/warnings in JBDS were intentionally ignored for the sake of nice diff. WFK had been EOL'd and this quickstart was moved under EAP, unfortunately without actual engineering support. Thus it was not maintained since then. > Failing quickstart [spring-petclinic] for 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.0.0.Final > 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-4636) Failing quickstart [spring-petclinic] for WildFly-11

by Vojtech Prusa (JIRA)

Vojtech Prusa created JBDS-4636: ----------------------------------- Summary: Failing quickstart [spring-petclinic] for 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.0.0.Final 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] (JBIDE-25306) Remove OpenShift2 plugins and features

by Bob Davis (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25306?page=com.atlassian.jira.plugi... ] Bob Davis commented on JBIDE-25306: ----------------------------------- Didn't this cause a problem last time? As long as we don't lose any critical functionality that those plugins provide, I'm fine with it. How do we ensure that we still have the things we need? > Remove OpenShift2 plugins and features > -------------------------------------- > > Key: JBIDE-25306 > URL: https://issues.jboss.org/browse/JBIDE-25306 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.5.2.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25050: --------------------------------------- Still blocked by https://redhat.service-now.com/surl.do?n=PNT0085293. > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: jenkins > Fix For: 4.5.2.Final > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25050: --------------------------------------- Still blocked by https://redhat.service-now.com/surl.do?n=PNT0085293. > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: jenkins > Fix For: 4.5.2.Final > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25050: ---------------------------------- Comment: was deleted (was: Still blocked by https://redhat.service-now.com/surl.do?n=PNT0085293.) > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: jenkins > Fix For: 4.5.2.Final > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- 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