November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22225 at 11/3/16 6:37 PM: ------------------------------------------------------------------- [~jeffmaury] +1, we need to get things that basically work - even with smaller or larger flaws - in now. AM3 is the last chance to get new features in. And then I'm not convinced that the problems that we see are caused by the debugging. I faced this even without any debugging involved. was (Author: adietish): [~jeffmaury] +1, we need to get things that basically work - even with smaller or larger flaws - in now. AM3 is the last chance to get new features in. > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Jeff MAURY > Labels: debugging, new_and_noteworthy, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. > steps: https://www.youtube.com/watch?v=1cKPPQrlC4k&feature=youtu.be -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22225: ------------------------------------------ [~jeffmaury] +1, we need to get things that basically work - even with smaller or larger flaws - in now. AM3 is the last chance to get new features in. > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Jeff MAURY > Labels: debugging, new_and_noteworthy, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. > steps: https://www.youtube.com/watch?v=1cKPPQrlC4k&feature=youtu.be -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22773: ------------------------------------- The first portion of the error seems very strange to me. We typically use renameTo, which only usually fails when moving from one filesystem to another. However, here, the two paths are definitely starting with the same prefix, and the renameTo should work without error. C:\work\runtime-JBossTools\.metadata\.plugins\org.eclipse.wst.server.core\tmp1018478665720865429.MF to C:\work\runtime-JBossTools\.metadata\.plugins\org.jboss.ide.eclipse.as.core\test1@eap-app\deploy\ROOT.war\META-INF\MANIFEST.MF Both paths start with C:\work\runtime-JBossTools\.metadata\.plugins\ so there's no real reason for the renameTo to fail. And why the rsync fails is even more confusing. Is that because it's using cyg paths? or is that appropriate? > 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.4.2.AM3 > > 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.2.3#72005)

9 years, 5 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-4154?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-4154: ----------------------------------- I suspect this might be cause by something like https://github.com/eclipse/m2e-core/blob/master/org.eclipse.m2e.core/src/... My understanding is the embedded runtime is looking for bundles matching the org.slf4j.api name. > 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: maven, rpm > Affects Versions: 10.2.0.AM3 > Environment: RHEL7 64bit > Reporter: Lukáš Valach > Assignee: Fred Bricon > Priority: Critical > Fix For: 10.2.0.AM3 > > > 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] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov resolved JBIDE-22803. -------------------------------------- Resolution: Done [~adietish] it's fixed. I'm resolving it > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23437) Update Neon.1 TP to consume m2e 1.7.1

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-23437: ----------------------------------- Summary: Update Neon.1 TP to consume m2e 1.7.1 Key: JBIDE-23437 URL: https://issues.jboss.org/browse/JBIDE-23437 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build, target-platform Reporter: Fred Bricon -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23437) Update Neon.1 TP to consume m2e 1.7.1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23437?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-23437: -------------------------------- Description: Pick new m2e version from http://download.eclipse.org/technology/m2e/milestones/1.7/1.7.1.20161103-... > Update Neon.1 TP to consume m2e 1.7.1 > ------------------------------------- > > Key: JBIDE-23437 > URL: https://issues.jboss.org/browse/JBIDE-23437 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform > Reporter: Fred Bricon > > Pick new m2e version from http://download.eclipse.org/technology/m2e/milestones/1.7/1.7.1.20161103-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23437) Update Neon.1 TP to consume m2e 1.7.1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23437?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-23437: ----------------------------------- Assignee: Nick Boldt > Update Neon.1 TP to consume m2e 1.7.1 > ------------------------------------- > > Key: JBIDE-23437 > URL: https://issues.jboss.org/browse/JBIDE-23437 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform > Reporter: Fred Bricon > Assignee: Nick Boldt > > Pick new m2e version from http://download.eclipse.org/technology/m2e/milestones/1.7/1.7.1.20161103-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22225: ------------------------------------- Description: We should be able to start and connect the new debugger to a node.js application running on Openshift. steps: https://www.youtube.com/watch?v=1cKPPQrlC4k&feature=youtu.be was:We should be able to start and connect the new debugger to a node.js application running on Openshift. > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > Assignee: Jeff MAURY > Labels: debugging, new_and_noteworthy, openshift_v3 > Fix For: 4.4.2.AM3 > > Attachments: Screenshot from 2016-07-21 15-29-25.png > > > We should be able to start and connect the new debugger to a node.js application running on Openshift. > steps: https://www.youtube.com/watch?v=1cKPPQrlC4k&feature=youtu.be -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22969: ------------------------------------------ [~dbocharov] how far did you get with this? Are the CDK issues with proxies all resolved? > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM3 > > Attachments: proxy_settings.png, proxy_settings_2.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- 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