November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-23213: ----------------------------------- [~mmalina], we can update it pretty much up to the GA date before we release the docs. cc: [~supriya.bharadwaj] > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.AM3 > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23184: ------------------------------------------ [~dbocharov] I merged your patch for openshift-restclient-java into master. I also deployed the new client lib to repository.jboss.org. I'd love you to test the new artifact a bit (if it fixes this and works in general) and confirm this. This would allow us to release a 5.2.0.Final before freezing tomorrow. > Add Capability to Watch Projects > -------------------------------- > > Key: JBIDE-23184 > URL: https://issues.jboss.org/browse/JBIDE-23184 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM3 > > > Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch > $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= > {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} > {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23418) Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23418?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23418: ------------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23418 > URL: https://issues.jboss.org/browse/JBIDE-23418 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: all-ports-removed.png, service-port-0.png, service-port-1-pod-port-empty.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23418) Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23418?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-23418: ---------------------------------------- Assignee: Viacheslav Kabanovich > Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23418 > URL: https://issues.jboss.org/browse/JBIDE-23418 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: all-ports-removed.png, service-port-0.png, service-port-1-pod-port-empty.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23418) Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23418?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23418: ------------------------------------- Fix Version/s: 4.4.2.AM3 > Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23418 > URL: https://issues.jboss.org/browse/JBIDE-23418 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: all-ports-removed.png, service-port-0.png, service-port-1-pod-port-empty.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23418) Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23418?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23418: ------------------------------------------ [~scabanovich] thx! Tested it, works for me merged into master > Deploy image wizard: "Services and Routing Settings" page creates erroneous first port if all ports are removed > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23418 > URL: https://issues.jboss.org/browse/JBIDE-23418 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Attachments: all-ports-removed.png, service-port-0.png, service-port-1-pod-port-empty.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

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

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4149: ------------------------------------ Attaching new log [^eclipse_10.2-0.20161101.1258.log] Eclipse was running in debug mode. There is not either "lucene" nor "NoClassDefFoundError: org/slf4j/Logger" in the log, but maven doesn't work. > 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: maven, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: ClassNotFoundEx_20161102_095940.png, eclipse.log, eclipse_10.2-0.20161101.1258.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.3#72005)

8 years, 11 months

1
0
0 / 0

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

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4149: ------------------------------- Attachment: eclipse_10.2-0.20161101.1258.log > 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: maven, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: ClassNotFoundEx_20161102_095940.png, eclipse.log, eclipse_10.2-0.20161101.1258.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.3#72005)

8 years, 11 months

1
0
0 / 0

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

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4149: ------------------------------------ Error message in description is correct. I copied this message from eclipse console window, this message simply wasn't written to log. Today I get same error on another machine (rh-eclipse46-devstudio-10.2-0.20161101.1258.el7.x86_64.rpm). See this screenshot !ClassNotFoundEx_20161102_095940.png|thumbnail! There is eclipse on the left site, you can see the error in console. This error occurs after maven clean. On the right site there is standard output. I am not sure this is duplicity of JBDS-4133. > 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: maven, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: ClassNotFoundEx_20161102_095940.png, 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)

8 years, 11 months

1
0
0 / 0

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

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4149: ------------------------------- Attachment: ClassNotFoundEx_20161102_095940.png > 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: maven, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: ClassNotFoundEx_20161102_095940.png, 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)

8 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2016