November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4149) Could not use Maven - NoClassDefFoundError: org/slf4j/Logger

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4149: --------------------------------- Priority: Blocker (was: Major) > Could not use Maven - NoClassDefFoundError: org/slf4j/Logger > ------------------------------------------------------------ > > Key: JBDS-4149 > URL: https://issues.jboss.org/browse/JBDS-4149 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: eclipse.log, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46.repo > > > I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message: > {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.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23429) Jolokia JMX connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23429?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23429: ------------------------------------- Code is here: https://github.com/jbosstools/jbosstools-server/pull/451 > Jolokia JMX connection > ---------------------- > > Key: JBIDE-23429 > URL: https://issues.jboss.org/browse/JBIDE-23429 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.2.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > A jolokia JMX connection would be useful for some users, and could also be used to connect to JMX for an EAP behind openshift / cdk. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4149) Could not use Maven - NoClassDefFoundError: org/slf4j/Logger

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4149: --------------------------------- Fix Version/s: 10.2.0.AM3 > Could not use Maven - NoClassDefFoundError: org/slf4j/Logger > ------------------------------------------------------------ > > Key: JBDS-4149 > URL: https://issues.jboss.org/browse/JBDS-4149 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: eclipse.log, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46.repo > > > I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message: > {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.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23430) Run as -> Run on server -> browser might open too early causing http 404

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23430?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23430: ----------------------------------- Component/s: server > Run as -> Run on server -> browser might open too early causing http 404 > ------------------------------------------------------------------------ > > Key: JBIDE-23430 > URL: https://issues.jboss.org/browse/JBIDE-23430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Josef Ludvicek > Attachments: runas.png > > > There should be some mechanism to detect when application is succesfully deployed. > It is possible that on slow machine it starts to deploy and open internal web browser too early - before app is fully deployed. > Stepps: > * start eap server > * right click on app -> Run as -> run on server -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23430) Run as -> Run on server -> browser might open too early causing http 404

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23430?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23430: ----------------------------------- Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio)) Key: JBIDE-23430 (was: JBDS-4148) Docs QE Status: (was: NEW) Affects Version/s: 4.4.2.AM2 (was: 9.1.0.GA) > Run as -> Run on server -> browser might open too early causing http 404 > ------------------------------------------------------------------------ > > Key: JBIDE-23430 > URL: https://issues.jboss.org/browse/JBIDE-23430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.4.2.AM2 > Reporter: Josef Ludvicek > Attachments: runas.png > > > There should be some mechanism to detect when application is succesfully deployed. > It is possible that on slow machine it starts to deploy and open internal web browser too early - before app is fully deployed. > Stepps: > * start eap server > * right click on app -> Run as -> run on server -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23429) Jolokia JMX connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23429?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23429: ------------------------------------- Here are some basic examples to test: Standalone / on wf - eap 1) Start wildfly or eap on localhost / standalone.sh 2) Deploy jolokia's jolokia-war-1.3.5.war to the standalone/deployments 3) Open jmx explorer and create new jmx connection 4) Give a name, put http://localhost:8080/jolokia-war-1.3.5/ as url, and use POST method 5) Connect to the new connection, expand it, play in the UI Behind CDK + EAP: Reference doc: http://developers.redhat.com/blog/2016/03/30/jolokia-jvm-monitoring-in-op... 1) Start CDK 2) Enable port forwarding on openshift connection 3) Create jolokia connection as above, except: 4) Use this as url: https://<master_host>:8443/api/v1/namespaces/<project_name>/pods/https:<pod_name>:8778/proxy/jolokia 5) Make sure to use GET (POST doesn't fully work in this case) 6) Make sure to add Authorization / Bearer: blahblah to the headers section, as per the above document. This can be discoverd by using oc whoami –t after oc login 7) Expand jmx tree, play in UI, call an operation or two, probably shouldn't call jmx shutdown operation though ;) > Jolokia JMX connection > ---------------------- > > Key: JBIDE-23429 > URL: https://issues.jboss.org/browse/JBIDE-23429 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jmx > Affects Versions: 4.4.2.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.2.AM3 > > > A jolokia JMX connection would be useful for some users, and could also be used to connect to JMX for an EAP behind openshift / cdk. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23430) Run as -> Run on server -> browser might open too early causing http 404

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23430?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23430: -------------------------------------- Assignee: Rob Stryker > Run as -> Run on server -> browser might open too early causing http 404 > ------------------------------------------------------------------------ > > Key: JBIDE-23430 > URL: https://issues.jboss.org/browse/JBIDE-23430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM2 > Reporter: Josef Ludvicek > Assignee: Rob Stryker > Attachments: runas.png > > > There should be some mechanism to detect when application is succesfully deployed. > It is possible that on slow machine it starts to deploy and open internal web browser too early - before app is fully deployed. > Stepps: > * start eap server > * right click on app -> Run as -> run on server -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-956) Update the pom.xml to contain only neccessary versions

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-956?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-956. ----------------------------------- pushed to master > Update the pom.xml to contain only neccessary versions > ------------------------------------------------------ > > Key: JBTIS-956 > URL: https://issues.jboss.org/browse/JBTIS-956 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Final, 4.4.0.Alpha1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.4.0.Final > > > Currently the pom.xml contains declaration of versions which are in fact overridden by versions declared in integration stack update site. -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-23358: ------------------------------------------ It turned out that the logic is more difficult, than just showing `status.phase`. https://github.com/openshift/origin-web-console/blob/7c57218bb83964ba0aab... I'll try to implement it > OpenShift Explorer: Pod status is not reflecting reality > -------------------------------------------------------- > > Key: JBIDE-23358 > URL: https://issues.jboss.org/browse/JBIDE-23358 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: openshift_v3 > Fix For: 4.4.x > > Attachments: pod_status.png > > > When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help. > !pod_status.png! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4077: ---------------------------------- Possible PR to fix the above issue: https://github.com/jbosstools/jbosstools-integration-tests/pull/1652 > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Rastislav Wagner > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.2#72004)

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