March 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4340) Please make XML formatting optional

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4340?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4340: -------------------------------- Assignee: Jeff MAURY > Please make XML formatting optional > ----------------------------------- > > Key: JBDS-4340 > URL: https://issues.jboss.org/browse/JBDS-4340 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: 3rd-party-dependencies > Reporter: Rick Wagner > Assignee: Jeff MAURY > > A customer has expressed the desire to disable auto-formatting of XML. In the customer's words: > ".If I Change any formatting in XML mode and then open it in design mode and Switch back to XML again.It deletes all the formattiing." > Please consider making auto-formatting optional. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4320) Show Hyper-V even if it is not detected with link to documentation how to configure and use it with CDK 3

by Petra Sargent (JIRA)

[ https://issues.jboss.org/browse/JBDS-4320?page=com.atlassian.jira.plugin.... ] Petra Sargent commented on JBDS-4320: ------------------------------------- [~dgolovin] [~rkratky] Would you like to see Hyper-V installation in the devSuite Installation Guide? > Show Hyper-V even if it is not detected with link to documentation how to configure and use it with CDK 3 > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-4320 > URL: https://issues.jboss.org/browse/JBDS-4320 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.4.0.AM1 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.4.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-498) Failure to run image results in Container Not Found [EBZ#514425]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-498?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-498: ------------------------------ Fix Version/s: Oxygen (4.7) M7 (was: Oxygen (4.7)) > Failure to run image results in Container Not Found [EBZ#514425] > ---------------------------------------------------------------- > > Key: ERT-498 > URL: https://issues.jboss.org/browse/ERT-498 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 6.0.0, Docker, bzira > Fix For: Oxygen (4.7) M7 > > > Trying to run an invalid command in a container results in a Container Not Found message which is rather cryptic. In addition, any run console is left open for the invalid container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-489) LogStream and LogReader not closed properly [EBZ#513175]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-489?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-489: ------------------------------ Fix Version/s: (was: Oxygen (4.7)) > LogStream and LogReader not closed properly [EBZ#513175] > -------------------------------------------------------- > > Key: ERT-489 > URL: https://issues.jboss.org/browse/ERT-489 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Oxygen (4.7) M7 > > > Created attachment 267122 > console log > I don't know the steps to reproduce, > I restarted several times a container from the Docker Explorer view and also tried unsuccessfully to connect using JMX, then I notice these logs in the (Hibernate??) console: > 2017-03-06 16:51:09,320 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@71f8be7c not closed properly > 2017-03-06 16:51:09,326 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@7308249e not closed properly > 2017-03-06 16:52:32,482 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@264466d3 not closed properly > 2017-03-06 16:53:13,437 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@59ddd31f not closed properly > 2017-03-06 16:53:13,437 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@293ef016 not closed properly > 2017-03-06 16:54:31,468 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@74675bfa not closed properly > 2017-03-06 16:57:11,469 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@7f02296e not closed properly > 2017-03-06 17:21:27,815 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@76f4439 not closed properly > 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@4c912048 not closed properly > 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@2da4958a not closed properly > 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@5017428b not closed properly -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-489) LogStream and LogReader not closed properly [EBZ#513175]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-489?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-489. ------------------------------- Fix Version/s: Oxygen (4.7) Oxygen (4.7) M7 Resolution: Done > LogStream and LogReader not closed properly [EBZ#513175] > -------------------------------------------------------- > > Key: ERT-489 > URL: https://issues.jboss.org/browse/ERT-489 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Oxygen (4.7), Oxygen (4.7) M7 > > > Created attachment 267122 > console log > I don't know the steps to reproduce, > I restarted several times a container from the Docker Explorer view and also tried unsuccessfully to connect using JMX, then I notice these logs in the (Hibernate??) console: > 2017-03-06 16:51:09,320 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@71f8be7c not closed properly > 2017-03-06 16:51:09,326 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@7308249e not closed properly > 2017-03-06 16:52:32,482 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@264466d3 not closed properly > 2017-03-06 16:53:13,437 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@59ddd31f not closed properly > 2017-03-06 16:53:13,437 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@293ef016 not closed properly > 2017-03-06 16:54:31,468 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@74675bfa not closed properly > 2017-03-06 16:57:11,469 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@7f02296e not closed properly > 2017-03-06 17:21:27,815 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@76f4439 not closed properly > 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@4c912048 not closed properly > 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogReader - com.spotify.docker.client.LogReader@2da4958a not closed properly > 2017-03-06 17:21:27,816 WARN Finalizer com.spotify.docker.client.LogStream - com.spotify.docker.client.LogStream@5017428b not closed properly -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24138) Implement queryMbeans for Jolokia

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24138?page=com.atlassian.jira.plugi... ] Aurélien Pupier reassigned JBIDE-24138: --------------------------------------- Assignee: Aurélien Pupier > Implement queryMbeans for Jolokia > --------------------------------- > > Key: JBIDE-24138 > URL: https://issues.jboss.org/browse/JBIDE-24138 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.4.4.AM1 > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > > Currently JolokiaMBeanServerConnection.queryMBeans is not implemented > @Override > public Set<ObjectInstance> queryMBeans(ObjectName name, QueryExp query) throws IOException { > // TODO Auto-generated method stub > return null; > } -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24145) Command to tune memory requirements for a deployement

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24145?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24145: ------------------------------- Fix Version/s: 4.4.4.AM3 > Command to tune memory requirements for a deployement > ----------------------------------------------------- > > Key: JBIDE-24145 > URL: https://issues.jboss.org/browse/JBIDE-24145 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24144) When deploying user should be able to tune the memory requirements

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24144?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24144: ------------------------------- Fix Version/s: 4.4.4.AM3 > When deploying user should be able to tune the memory requirements > ------------------------------------------------------------------ > > Key: JBIDE-24144 > URL: https://issues.jboss.org/browse/JBIDE-24144 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3, wizard > Fix For: 4.4.4.AM3 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24147) Pipeline view support

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-24147: ---------------------------------- Summary: Pipeline view support Key: JBIDE-24147 URL: https://issues.jboss.org/browse/JBIDE-24147 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.4.AM2 Reporter: Jeff MAURY -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-24146: ---------------------------------- Summary: Support pipeline deployment style Key: JBIDE-24146 URL: https://issues.jboss.org/browse/JBIDE-24146 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.4.4.AM2 Reporter: Jeff MAURY -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 March 2017