May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22378) Server editor: cannot edit the route

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22378?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22378: ------------------------------------- Description: The server editor wont allow the user to edit the route: !server-editor.png! > Server editor: cannot edit the route > ------------------------------------ > > Key: JBIDE-22378 > URL: https://issues.jboss.org/browse/JBIDE-22378 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor > > The server editor wont allow the user to edit the route: > !server-editor.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3873) DevStudio 10.0.0.Alpha1 points to 9.0 update site

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3873?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3873. ------------------------------- Verified in jboss-devstudio-10.0.0.Alpha1-v20160518-1105-B5380-installer-standalone.jar > DevStudio 10.0.0.Alpha1 points to 9.0 update site > ------------------------------------------------- > > Key: JBDS-3873 > URL: https://issues.jboss.org/browse/JBDS-3873 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha2 > > > I'm not sure exactly where this jira belongs. But I'm sure Nick will know :) > I just installed DevStudio 10.0.0.Alpha1 B5251 and when I go to Help -> Install New Software, I can see that the only update site that is set up is: > https://devstudio.redhat.com/9.0/stable/updates/ > I know that there is probably nothing at /10.0/ yet, but at some point we will want to move to that URL. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Thomas Mäder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-22376: -------------------------------------- What I'm doing right now is just assume that remoting-jmx is available on port 9999 (and set up the forwarding when starting debug mode). This will either work or fail with a warning in the log. > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Thomas Mäder > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Josephine Qian edited comment on JBDS-3787 at 5/18/16 10:03 AM: ---------------------------------------------------------------- [~dgolovin] Great! Let me know if you have any questions as you implement. FYI, you might be able to borrow the error message implementation from PatternFly (color, border, spacing...). https://www.patternfly.org/widgets/#forms -- Regarding the warning for vagrant version, I thought we made a decision last time, did we? I am trying to recall...if the version is not what we recommend, then we will force users to install vagrant again, correct? If so, our goal is just to provide a little bit info to users about the detected vagrant, so they won't spend time wondering why they have to install again...is that what you are thinking? Looping [~jowilson] in, just in case I missed anything we discussed before. was (Author: joqian): Great! Let me know if you have any questions as you implement. -- Regarding the warning for vagrant version, I thought we made a decision last time, did we? I am trying to recall...if the version is not what we recommend, then we will force users to install vagrant again, correct? If so, our goal is just to provide a little bit info to users about the detected vagrant, so they won't spend time wondering why they have to install again...is that what you are thinking? Looping [~jowilson] in, just in case I missed anything we discussed before. > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Josephine Qian commented on JBDS-3787: -------------------------------------- Great! Let me know if you have any questions as you implement. -- Regarding the warning for vagrant version, I thought we made a decision last time, did we? I am trying to recall...if the version is not what we recommend, then we will force users to install vagrant again, correct? If so, our goal is just to provide a little bit info to users about the detected vagrant, so they won't spend time wondering why they have to install again...is that what you are thinking? Looping [~jowilson] in, just in case I missed anything we discussed before. > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: components are optional v1.png > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21408) JBDS frozen and CPU at 100% after running overnight

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21408?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21408: --------------------------------------- I haven't experienced this ever since. > JBDS frozen and CPU at 100% after running overnight > --------------------------------------------------- > > Key: JBIDE-21408 > URL: https://issues.jboss.org/browse/JBIDE-21408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > Attachments: frozen_jbds_jstack.txt > > > Yesterday I kept JBDS 9.1.0.Beta1 running on my laptop (OS X) and I locked the laptop when I left the office. I couldn't find any Wake entries in the logs, so I think it did not sleep, but I'm not 100% sure. > Today when I unlocked my laptop, the JBDS icon jumped in the Dock, meaning there was some pop up or something, but from then, the app is frozen and takes 100% CPU. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-654: ----------------------------------------- That's a good question and a logical extension of this conversation. Can I suggest that we start with the Fuse tooling + runtime installer we've been discussing and use it as a pilot to see if it gets any traction? If it does, we can float this to other product teams as well. Is there any way to track not just downloads but how many time it gets run? We already do some tracking in the tooling... but I would think download tracking of the installer would be one metric we could pretty easily keep track of. > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > 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: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22377) Jax RS service - Run on Server: default id value is ignored in WS tester

by Jan Richter (JIRA)

Jan Richter created JBIDE-22377: ----------------------------------- Summary: Jax RS service - Run on Server: default id value is ignored in WS tester Key: JBIDE-22377 URL: https://issues.jboss.org/browse/JBIDE-22377 Project: Tools (JBoss Tools) Issue Type: Bug Components: webservices Affects Versions: 4.4.0.Alpha1 Reporter: Jan Richter I have a project with the following jax-rs service: {noformat} @Path("/rest") public class Service { @GET @Path("/{id}") public String mainService(@PathParam("id") @DefaultValue("0") Integer id, @MatrixParam("m1") @DefaultValue("m1") String m1, @QueryParam("q1") @DefaultValue("q1") String q1) { return id + " " + m1 + " " + q1; } } {noformat} When I select 'run on server' on the service endpoint and then invoke the opened service tester, it shows blank id value even when the default is set to 0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22243: --------------------------------------- This is probably true, but given our current design, it is not easy to fix. > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22376: --------------------------------------- Docker files can include labels which in theory could be brought forward from the built image to the pod resource. I don't know if that happens now, but it would be a way to inspect a pod to determine its server type. Also, if we include either templates or builder images, we could add labels or annotations there which could also provide a hint to us. > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Thomas Mäder > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- 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