June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22646) Starting cdk creates two processes in debug view

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22646?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22646: -------------------------------- Fix Version/s: 4.4.1.M1 > Starting cdk creates two processes in debug view > ------------------------------------------------ > > Key: JBIDE-22646 > URL: https://issues.jboss.org/browse/JBIDE-22646 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.M1 > > > Starting cdk creates two processes in debug view. > One does not disappear when the startup process is complete. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22635) Deprecate / Remove the Server Log View

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22635?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22635: ----------------------------------- Assignee: Rob Stryker > Deprecate / Remove the Server Log View > -------------------------------------- > > Key: JBIDE-22635 > URL: https://issues.jboss.org/browse/JBIDE-22635 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.M1 > Reporter: Rob Stryker > Assignee: Rob Stryker > > Deprecate and remove the Server Log View. > The Server Log View was originally designed to allow a custom "Error Log" to be filled with information that wasn't just "errors" but more like tracing what the server adapter was doing. > In it's original form, it held all status warnings and errors, and users never saw them. Eventually, we started also sending the status objects to the official Error Log, so users may see them. Once that happened, the Server Log view became completely redundant. It's only benefits were that it occasionally over-logged stuff that wasn't appropriate to send to the main error log... but it's API / extension points were kinda ugly, and it overall isn't very useful any longer. > Also, other server adapters have requested we remove the action at least, for their server types, since they never use the Server Log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-795) JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-795?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-795: ----------------------------------------- Can I see an example of what they're referring to as far as "given an id without user input"? Is this in the Camel editor? Or the SwitchYard editor? > JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default > ---------------------------------------------------------------------------- > > Key: JBTIS-795 > URL: https://issues.jboss.org/browse/JBTIS-795 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1 with devstudio-integration-stack-9.0.0.Beta1-earlyaccess.zip > Reporter: Rick Wagner > > A user has noted that Camel routes used in SwitchYard are now being given an Id without user input. This is a changed behavior. > The same user complains of very slow loading of SwitchYard/Camel component routes, but this is still under investigation in the cited support ticket. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Ilya Buziuk edited comment on JBIDE-22362 at 6/23/16 5:08 PM: -------------------------------------------------------------- [~adietish], I found an issue with setting DEV_MODE by default. Basically, [OpenShiftLaunchController|https://github.com/jbosstools/jbosstools-opensh...] which is responsible for running server adapter enables / disables [DebuggingContext|https://github.com/jbosstools/jbosstools-openshift/blob/...] depending on DEV_MODE env var. The contract is the following - if either DEV_MODE (node) or DEBUG (eap / java) are true, debugging context is enabled. I have implemented setting DEV_MODE to true by default, but after restarting server in debug mode it does not working correctly - https://github.com/ibuziuk/jbosstools-openshift/commit/d419c9d3da26ad4cc5... Any ideas how can this be tackled? I can not figure out how can we enable DEV_MODE without affecting DebuggingContext was (Author: ibuziuk): [~adietish], I fond an issue with setting DEV_MODE by default. Basically, [OpenShiftLaunchController|https://github.com/jbosstools/jbosstools-opensh...] which is responsible for running server adapter enables / disables [DebuggingContext|https://github.com/jbosstools/jbosstools-openshift/blob/...] depending on DEV_MODE env var. The contract is the following - if either DEV_MODE (node) or DEBUG (eap / java) are true, debugging context is enabled. I have implemented setting DEV_MODE to true by default, but after restarting server in debug mode it does not working correctly - https://github.com/ibuziuk/jbosstools-openshift/commit/d419c9d3da26ad4cc5... Any ideas how can this be tackled? I can not figure out how can we enable DEV_MODE without affecting DebuggingContext > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.M1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-22362: ------------------------------------- [~adietish], I fond an issue with setting DEV_MODE by default. Basically, [OpenShiftLaunchController|https://github.com/jbosstools/jbosstools-opensh...] which is responsible for running server adapter enables / disables [DebuggingContext|https://github.com/jbosstools/jbosstools-openshift/blob/...] depending on DEV_MODE env var. The contract is the following - if either DEV_MODE (node) or DEBUG (eap / java) are true, debugging context is enabled. I have implemented setting DEV_MODE to true by default, but after restarting server in debug mode it does not working correctly - https://github.com/ibuziuk/jbosstools-openshift/commit/d419c9d3da26ad4cc5... Any ideas how can this be tackled? I can not figure out how can we enable DEV_MODE without affecting DebuggingContext > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.M1 > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-795) JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default

by Rick Wagner (JIRA)

Rick Wagner created JBTIS-795: --------------------------------- Summary: JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default Key: JBTIS-795 URL: https://issues.jboss.org/browse/JBTIS-795 Project: JBoss Tools Integration Stack Issue Type: Bug Components: Fuse IDE Affects Versions: 9.0.0.Beta1 Environment: JBDS 9.1 with devstudio-integration-stack-9.0.0.Beta1-earlyaccess.zip Reporter: Rick Wagner A user has noted that Camel routes used in SwitchYard are now being given an Id without user input. This is a changed behavior. The same user complains of very slow loading of SwitchYard/Camel component routes, but this is still under investigation in the cited support ticket. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22646) Starting cdk creates two processes in debug view

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-22646: ----------------------------------- Summary: Starting cdk creates two processes in debug view Key: JBIDE-22646 URL: https://issues.jboss.org/browse/JBIDE-22646 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdk, server Affects Versions: 4.4.1.M1 Reporter: Rob Stryker Starting cdk creates two processes in debug view. One does not disappear when the startup process is complete. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-751) Inconsistent presentation of jar file names in 'Install Red Hat JBoss Developer Studio'

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-751?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-751: ------------------------------------- You could also link users directly to this page so they'd see the 'building from source zip' instructions more quickly. https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > Inconsistent presentation of jar file names in 'Install Red Hat JBoss Developer Studio' > --------------------------------------------------------------------------------------- > > Key: TOOLSDOC-751 > URL: https://issues.jboss.org/browse/TOOLSDOC-751 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: Installation Guide > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Misha Ali > > Looking in https://access.redhat.com/articles/2358611 I see that we have two different ways of presenting the jar filenames: > {code} > devstudio-<version>-installer-standalone.jar > {code} > and > {code} > devstudio-version-installer-standalone.jar > devstudio-version-installer-eap.jar > {code} > Additionally, the correct filename for the installer sources [1] is: > {code} > devstudio-<version>-src.zip > {code} > not > {code} > devstudio-<version>-installer-src.zip > {code} > [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... > Note that the instructions for building from source should also mention that it's way easier to build from github sources [2] than the src zip, since we plan to eliminate the src zip entirely in a future release. > [2] https://github.com/jbdevstudio/jbdevstudio-product -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-751) Inconsistent presentation of jar file names in 'Install Red Hat JBoss Developer Studio'

by Nick Boldt (JIRA)

Nick Boldt created TOOLSDOC-751: ----------------------------------- Summary: Inconsistent presentation of jar file names in 'Install Red Hat JBoss Developer Studio' Key: TOOLSDOC-751 URL: https://issues.jboss.org/browse/TOOLSDOC-751 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Components: Installation Guide Affects Versions: 10.0.0.GA Reporter: Nick Boldt Assignee: Misha Ali Looking in https://access.redhat.com/articles/2358611 I see that we have two different ways of presenting the jar filenames: {code} devstudio-<version>-installer-standalone.jar {code} and {code} devstudio-version-installer-standalone.jar devstudio-version-installer-eap.jar {code} Additionally, the correct filename for the installer sources [1] is: {code} devstudio-<version>-src.zip {code} not {code} devstudio-<version>-installer-src.zip {code} [1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... Note that the instructions for building from source should also mention that it's way easier to build from github sources [2] than the src zip, since we plan to eliminate the src zip entirely in a future release. [2] https://github.com/jbdevstudio/jbdevstudio-product -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-750) Wrong URL in 'Update Red Hat JBoss Developer Studio'

by Nick Boldt (JIRA)

Nick Boldt created TOOLSDOC-750: ----------------------------------- Summary: Wrong URL in 'Update Red Hat JBoss Developer Studio' Key: TOOLSDOC-750 URL: https://issues.jboss.org/browse/TOOLSDOC-750 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Components: Update Affects Versions: 10.0.0.GA Reporter: Nick Boldt Assignee: Misha Ali Looking in https://access.redhat.com/articles/2360061 I see that the URL shown for devstudio 10 updates is... https://devstudio.redhat.com/updates/9.0/ Doc should perhaps be rewritten to emphasize devstudio 10, not devstudio 9.0, 9.1, and 9.y. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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