May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-674: ------------------------------------------- okey - but we always had these under the runtime tooling they were for too, right ? so the isntall approach is not changing is just that we don't have them available in a standalone category. > Deprecate 'SOA 5.x Compatibility' tooling > ----------------------------------------- > > Key: JBTIS-674 > URL: https://issues.jboss.org/browse/JBTIS-674 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final, 9.0.0.GA > > Attachments: dep1.png, dep2.png, dep3.png, dep4.png, dep5.png > > > The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of: > org.guvnor.tools.feature > org.jboss.tools.esb.feature > org.jboss.tools.jbpm3.feature > org.jboss.tools.jbpm.common.feature > org.jboss.tools.jbpm.convert.feature > The runtime detector features will not be deprecated: > org.jboss.tools.runtime.drools.detector.feature > org.jboss.tools.runtime.esb.detector.feature > org.jboss.tools.runtime.jbpm.detector.feature > FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22227) Hotcode replace fails on local wildfly if breakpoint is set

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22227?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22227: --------------------------------------------- where does eclipse gain a reference ? so far my understanding is that it does not have a reference but tat when asking the debugger to replace classes it does it on *all* classes including old classes not yet garbage collected. If you say bug is caused by eclipse does that imply that this does not behave the same way using netbeans or intellij ? > Hotcode replace fails on local wildfly if breakpoint is set > ----------------------------------------------------------- > > Key: JBIDE-22227 > URL: https://issues.jboss.org/browse/JBIDE-22227 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > When debugging a local wildfly server with a deployed servlet, making a breaking change such as method name or signature will fail. > This will pop up a dialog asking to restart the module or the server, which is expected. However, after that, non-breaking changes will still also pop up the hotcode-failed dialog, when it shouldn't. > Workflow: > 1) Create a dynamic web project with simple servlet > 2) Start a wildfly 10 in debug mode and deploy the web project > 3) Run-on-server the servlet object and verify it shows expected output > 4) Set a breakpoint inside the doGet() method > 5) refresh browser (breakpoint gets hit), press play > 6) Make a non-breaking change (change text inside doGet()) > 7) refresh website, verify breakpoint is hit, website content is updated > 8) make a breaking change by adding a new method > 9) hotcode-replace dialog appears. Press 'restart module' > 10) refresh web browser, verify breakpoint is hit, output has changed as expected > 11) make a non-breaking change in output of doGet() > 12) ASSERT: hotcode replace dialog does NOT show - THIS STEP FAILS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22288: ------------------------------------- [~psrna] awesome, thanks! According to the logs *(Problematic frame:# C [libplds4.so+0x1697])* this one is very likely to be coupled with Webkit / Xulrunner conflict - https://issues.jboss.org/browse/JBIDE-9144 > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-22288: ------------------------------------ Hi [~ibuziuk], the VPE QE owner is to be reassign again. I'll look at the issue. -P > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-688) Rebuild JBDS-IS build to include new Drools/jBPM plugin

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-688?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-688: ------------------------------------ Description: Currently, there is Drools 6.4.0.Final. But Bob and Kris want to include some bug fixes (see JBTIS-686) and ask for including the version 6.4.1.Final. QE is now verifying the bug fixes and found some issues. Here we will discuss whether we include version 6.4.1.Final into JBDS-IS 9.0.0.GA or not. Note that we cannot include Drools 6.3.1.Final since this version wasn't tested with JBDS 9.1.0.GA. was: Currently, there is Drools 6.4.0.Final. Bug Bob and Kris want to include some bug fixes (see JBTIS-686) and ask for including the version 6.4.1.Final. QE is now verifying the bug fixes and found some issues. Here we will discuss whether we include version 6.4.1.Final into JBDS-IS 9.0.0.GA or not. Note that we cannot include Drools 6.3.1.Final since this version wasn't tested with JBDS 9.1.0.GA. > Rebuild JBDS-IS build to include new Drools/jBPM plugin > ------------------------------------------------------- > > Key: JBTIS-688 > URL: https://issues.jboss.org/browse/JBTIS-688 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Currently, there is Drools 6.4.0.Final. But Bob and Kris want to include some bug fixes (see JBTIS-686) and ask for including the version 6.4.1.Final. > QE is now verifying the bug fixes and found some issues. Here we will discuss whether we include version 6.4.1.Final into JBDS-IS 9.0.0.GA or not. > Note that we cannot include Drools 6.3.1.Final since this version wasn't tested with JBDS 9.1.0.GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22005: --------------------------------------- [~mlabuda] have you seen this one recently to know if we can determine it to be a connection timeout? > Log console: Unexpected EOF in pod log > -------------------------------------- > > Key: JBIDE-22005 > URL: https://issues.jboss.org/browse/JBIDE-22005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.0.Alpha2 > > > I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log. > Last lines from console (output of application pod log) > {code} > ... > [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe... > error: unexpected EOF > {code} > I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22005) Log console: Unexpected EOF in pod log

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22005?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-22005: ---------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Log console: Unexpected EOF in pod log > -------------------------------------- > > Key: JBIDE-22005 > URL: https://issues.jboss.org/browse/JBIDE-22005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.0.Alpha2 > > > I had an eap application running on OpenShift. I was watching pod log of the application (stdout from EAP server). Unfortunately in some point console was not enough for displaying pod log and it stopped streaming pod log. > Last lines from console (output of application pod log) > {code} > ... > [0m[33m09:27:29,845 WARN [org.jgroups.protocols.openshift.KUBE_PING] (Timer-4,shared=tcp) Problem getting Pod json from Kubernetes Client[masterUrl=https://172.30.0.1:443/api/v1, headers={Authorization=#MASKED:885#}, connectTimeout=5000, readTimeout=30000, operationAttempts=3, operationSleep=1000, streamProvider=org.openshift.ping.common.stream.InsecureStreamProvider@4fb96d85] for cluster [hornetq-channel], namespace [serveradaptertrests], labels [application=eap-app]; encountered [java.lang.Exception: 3 attempt(s) with a 1000ms sleep to execute [OpenStream] failed. Last failure was [java.io.IOException: Server returned HTTP response code: 403 for URL: https://172.30.0.1:443/api/v1/namespaces/serveradaptertrests/pods?labelSe... > error: unexpected EOF > {code} > I also checked pod log via Web UI, whether there is something wrong on OpenShift side, but it is tooling related - memory/space for pod log output in console is limited and it went "out of memory". Pod log in Web UI was streaming all the time. This block user from checking pod log once it reach a specific length. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16301) No combo to select Target Runtime in examples dilaog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16301?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16301: -------------------------------- Fix Version/s: LATER (was: 4.3.x) > No combo to select Target Runtime in examples dilaog > ---------------------------------------------------- > > Key: JBIDE-16301 > URL: https://issues.jboss.org/browse/JBIDE-16301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.Final > Reporter: Denis Golovin > Fix For: LATER > > Attachments: Selection_025.png > > > Target Runtime combo is not visible in Examples dialog > !Selection_025.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16071: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.x) Story Points: 8 > Duplicate cheat sheet options in Project Examples Preferences > ------------------------------------------------------------- > > Key: JBIDE-16071 > URL: https://issues.jboss.org/browse/JBIDE-16071 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: Central_cheatsheet.png > > > Click Window > Preferences > JBoss Tools > Project Examples. > The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior. > !Central_cheatsheet.png! > I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13287) examples URLs should use major/minor/service/milestone convention

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13287?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13287: -------------------------------- Fix Version/s: 4.4.x (was: 4.2.x) > examples URLs should use major/minor/service/milestone convention > ------------------------------------------------------------------ > > Key: JBIDE-13287 > URL: https://issues.jboss.org/browse/JBIDE-13287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.4.x > > > Instead of > {code:title=http://download.jboss.org/jbosstools/examples/} > project-examples-community-4.0.GA.xml > project-examples-jbds60.xml > project-examples-maven-4.0.GA.xml > project-examples-shared-4.0.GA.xml > ... > {code} > We should consider using something like 6/1/0/Alpha1/project-examples*.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016