January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4633) Use Tycho 1.1 so we can build with JDK 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4633?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4633: ----------------------------- Fix Version/s: 11.3.0.AM1 (was: 11.x) > Use Tycho 1.1 so we can build with JDK 9 > ---------------------------------------- > > Key: JBDS-4633 > URL: https://issues.jboss.org/browse/JBDS-4633 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, upstream > Affects Versions: 11.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.3.0.AM1 > > > Once Tycho 1.1 is out, we should use that so we can build with JDK 9. > https://wiki.eclipse.org/Tycho/Release_Notes/1.1 > Issues: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=514471#c22 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=528242 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=514119#c14 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 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: 4.5.3.AM1 (was: 4.5.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.3.AM1 > > > 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)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4633) Use Tycho 1.1 so we can build with JDK 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4633?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4633: ---------------------------------- With Tycho 1.1.0-SNAPSHOT about to be released as 1.1.0, here are some JDK9-based jobs for Base, Server, Openshift, Central/Maven, and Hibernate: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Use Tycho 1.1 so we can build with JDK 9 > ---------------------------------------- > > Key: JBDS-4633 > URL: https://issues.jboss.org/browse/JBDS-4633 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, upstream > Affects Versions: 11.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > Once Tycho 1.1 is out, we should use that so we can build with JDK 9. > https://wiki.eclipse.org/Tycho/Release_Notes/1.1 > Issues: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=514471#c22 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=528242 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=514119#c14 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 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: ------------------------------------ With Tycho 1.1.0-SNAPSHOT about to be released as 1.1.0, here are some JDK9-based jobs for Base, Server, Openshift, Central/Maven, and Hibernate: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > 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.x > > > 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)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-22773: ------------------------------------ Attachment: similarErrorWithFuseTemplates.png > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.5.3.AM1 > > Attachments: screenshot-1.png, similarErrorWithFuseTemplates.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-22773: ----------------------------------------- !similarErrorWithFuseTemplates.png|thumbnail! > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.5.3.AM1 > > Attachments: screenshot-1.png, similarErrorWithFuseTemplates.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-25674: ----------------------------------------- the jar of JBoss Tools Jolokia is 1.10.2.v20171121-1701 > NPE in JolokiaConnectionWrapper.extractStatus > --------------------------------------------- > > Key: JBIDE-25674 > URL: https://issues.jboss.org/browse/JBIDE-25674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Aurélien Pupier > > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {noformat} > I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable" > in this case the "response" is null > 2 possibilities: > - it is normal that it is null in this case Jboss Tools need to handle this case > - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25674?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-25674: ------------------------------------ Component/s: jmx > NPE in JolokiaConnectionWrapper.extractStatus > --------------------------------------------- > > Key: JBIDE-25674 > URL: https://issues.jboss.org/browse/JBIDE-25674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Reporter: Aurélien Pupier > > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {noformat} > I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable" > in this case the "response" is null > 2 possibilities: > - it is normal that it is null in this case Jboss Tools need to handle this case > - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-22773 at 1/29/18 10:00 AM: -------------------------------------------------------------- [~aurelien.pupier] then can you point me to the correct screenshot ? was (Author: jeffmaury): [~aurelien.pupier] then ca you point me to the correct screenshot ? > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.5.3.AM1 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25674) NPE in JolokiaConnectionWrapper.extractStatus

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-25674: --------------------------------------- Summary: NPE in JolokiaConnectionWrapper.extractStatus Key: JBIDE-25674 URL: https://issues.jboss.org/browse/JBIDE-25674 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Aurélien Pupier {noformat} !ENTRY org.eclipse.core.jobs 4 2 2018-01-29 15:56:34.020 !MESSAGE An internal error occurred during: "Connect Job". !STACK 0 java.lang.NullPointerException at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.extractStatus(JolokiaConnectionWrapper.java:340) at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324) at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113) at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {noformat} I put a breakpoint in org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable() to see which exception it was and it is a "503 Service Unavailable" in this case the "response" is null 2 possibilities: - it is normal that it is null in this case Jboss Tools need to handle this case - it is not normal that it is null and in this case, it needs to be reported upstream (even if a null check might nice as a workaround for now) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2018