November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21836: -------------------------------- Fix Version/s: 4.4.2.AM3 (was: 4.4.x) > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.2.AM3 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21836. --------------------------------- Resolution: Cannot Reproduce Nobody can reproduce this. I would love for QE to re-open if its possible, but I think it's time we close this issue. > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.4.2.AM3 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21812) Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21812?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21812: ------------------------------------- [~mmalina] Can you test this? My tests show attempting to start with openjdk 8 seems to freeze, and we can handle that better... but assuming we use a jdk 7, i have been unable to replicate this error case. > Management error reported connecting JBoss Tools 4.3 to JBoss AS 7.1.1 > ---------------------------------------------------------------------- > > Key: JBIDE-21812 > URL: https://issues.jboss.org/browse/JBIDE-21812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta2 > Environment: JBoss AS 7.1.1 > Eclipse Mars.2 4.5.2 > IPv4 stack specified > Local host connectivity (127.0.0.1 specified) > Reporter: William Darby > Assignee: Rob Stryker > Fix For: 4.4.x > > Attachments: eclipse.log > > > When starting JBoss from within Eclipse the following error appears on the console: > 17:25:23,182 ERROR [org.jboss.remoting.remote.connection] (Remoting "hostname:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: An established connection was aborted by the software in your host machine > This occurs with or without firewall/anti-virus enabled. > And with the startup/shutdown pollers set to Management Service or Web Port. > Also with Server Ports specified or 'Detected from Local Runtime' > It occurs occasionally on the first server startup, but repeatedly after stopping and restarting the server. > It also occurs when the 'Server Details' are browsed in the Servers view, i.e., selecting any folder will cause another of the errors to display. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23470: ------------------------------------------ [~rob.stryker] happened also when you restarted server adapter in debug mode? or? > Server Adapter: stuck restarting in debug mode > ---------------------------------------------- > > Key: JBIDE-23470 > URL: https://issues.jboss.org/browse/JBIDE-23470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23468) otherOS jobs need to update test pattern to include itests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23468?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23468: ------------------------------------ In other news, working on a better approach to runnning the javaee tests on win/osx: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > otherOS jobs need to update test pattern to include itests > ---------------------------------------------------------- > > Key: JBIDE-23468 > URL: https://issues.jboss.org/browse/JBIDE-23468 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.AM3 > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > Subject is enough. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4154) JavaEE Web Project > Run As > Maven not working

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4154?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4154: ---------------------------------- Need to get the latest m2e 1.7.1 into the devstudio rpm so you don't have to update from rpm to latest m1e 1.7.1. So this issue can be resolved only once we have the target platform updated. Steps: a) release AM3 tomorrow once QE signs off b) update target platform to include latest m2e and other queued fixes (eg., lucene, thym) c) rebuild everything d) verify this issue is fixed OOTB w/o workaround or update/patch fix. > JavaEE Web Project > Run As > Maven not working > ----------------------------------------------- > > Key: JBDS-4154 > URL: https://issues.jboss.org/browse/JBDS-4154 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, maven, rpm, target-platform > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Critical > Fix For: 10.2.0.GA > > Attachments: maven171-fix-installed.png, maven171-fix.png > > > I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message in Console (nothing in Error log): > {code} > Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) > at java.lang.Class.privateGetMethodRecursive(Class.java:3048) > at java.lang.Class.getMethod0(Class.java:3018) > at java.lang.Class.getMethod(Class.java:1784) > at org.codehaus.plexus.classworlds.launcher.Launcher.getEnhancedMainMethod(Launcher.java:172) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:268) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger > at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) > ... 10 more > {code} > Standalone maven installation works fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4154) JavaEE Web Project > Run As > Maven not working

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4154?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4154: -------------------------------- Assignee: Nick Boldt (was: Fred Bricon) > JavaEE Web Project > Run As > Maven not working > ----------------------------------------------- > > Key: JBDS-4154 > URL: https://issues.jboss.org/browse/JBDS-4154 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, maven, rpm, target-platform > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.2.0.GA > > Attachments: maven171-fix-installed.png, maven171-fix.png > > > I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message in Console (nothing in Error log): > {code} > Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) > at java.lang.Class.privateGetMethodRecursive(Class.java:3048) > at java.lang.Class.getMethod0(Class.java:3018) > at java.lang.Class.getMethod(Class.java:1784) > at org.codehaus.plexus.classworlds.launcher.Launcher.getEnhancedMainMethod(Launcher.java:172) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:268) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) > Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger > at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) > at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) > at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) > ... 10 more > {code} > Standalone maven installation works fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4166) Cygwin detection configures wrong location if there are more than one cygwin installation is in PATH

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4166: ----------------------------------- Summary: Cygwin detection configures wrong location if there are more than one cygwin installation is in PATH Key: JBDS-4166 URL: https://issues.jboss.org/browse/JBDS-4166 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.2.0.AM3 Environment: Windows Reporter: Denis Golovin Priority: Minor Vagrant will use previously installed sygwins not installed one in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4166) Cygwin detection configures wrong location if there are more than one cygwin installation is in PATH

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4166?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4166: ----------------------------------- Assignee: Denis Golovin > Cygwin detection configures wrong location if there are more than one cygwin installation is in PATH > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-4166 > URL: https://issues.jboss.org/browse/JBDS-4166 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM3 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > > Vagrant will use previously installed sygwins not installed one in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4164) Project Examples don't work behind proxy

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4164?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-4164: ------------------------------------ Assignee: Snjezana Peco > Project Examples don't work behind proxy > ---------------------------------------- > > Key: JBDS-4164 > URL: https://issues.jboss.org/browse/JBDS-4164 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jbpm, project-examples > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Snjezana Peco > > Issue is reported on forum (see [forum reference|https://developer.jboss.org/message/964401#964401]). Examples does not work behind proxy with eclipse configured to use proxy in settings. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 November 2016