June 2016 - jbosstools-issues - Jboss List Archives

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

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-22635: ----------------------------------- Summary: 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.S116 Reporter: 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] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19081: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/167, https://github.com/jbosstools/jbosstools-javaee/pull/398, https://github.com/jbosstools/jbosstools-jst/pull/565 (was: https://github.com/jbosstools/jbosstools-build/pull/167, https://github.com/jbosstools/jbosstools-javaee/pull/398) > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19081: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/167, https://github.com/jbosstools/jbosstools-javaee/pull/398 (was: https://github.com/jbosstools/jbosstools-build/pull/167) > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22633) jbosstools-multiple.target has multiple incompatible IUs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22633?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22633: ------------------------------------ If this is urgent, please throw me a PR to make it happen faster. > jbosstools-multiple.target has multiple incompatible IUs > -------------------------------------------------------- > > Key: JBIDE-22633 > URL: https://issues.jboss.org/browse/JBIDE-22633 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Reporter: Paul Leacu > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.S116 > > > Please correct the jbosstools-multiple.target to avoid the duplication of the IU as this is causing build failures in both SwitchYard and Fuse Tooling (development). > https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/... > org.eclipse.egit.ui.smartimport is defined twice with two different versions: > {code} > [ERROR] Resolution failed: > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2 > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-318) Add privileged support to ContainerLauncher class launch method [EBZ#496515]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-318?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-318. ------------------------------- Fix Version/s: Neon (4.6).1 Resolution: Done > Add privileged support to ContainerLauncher class launch method [EBZ#496515] > ---------------------------------------------------------------------------- > > Key: ERT-318 > URL: https://issues.jboss.org/browse/ERT-318 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Nick Boldt > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6), Neon (4.6).1 > > > Support for the privileged flag is not possible with the current ContainerLauncher.launch method. A change was posted, but it was too late for the major 5.0.0 release. It will be modified for 5.1.0 to simply add API rather than remove or change API. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-317) Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-317?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-317. ------------------------------- Fix Version/s: Neon (4.6).1 Resolution: Done > Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333] > --------------------------------------------------------------------------- > > Key: ERT-317 > URL: https://issues.jboss.org/browse/ERT-317 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Nick Boldt > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6), Neon (4.6).1 > > > The string used for the CMD for a Run Image configuration changes each time it is opened. The first time it strips off one set of quotes, the second time it strips off the next, etc.. > The CMD string should appear the same each time the configuration is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-312) show in web browser uses external webbrowser now - not whatever eclipse is configured for [EBZ#496487]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-312?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-312: -------------------------------- Sprint: devex #116 2016/06/15 - 07/05 > show in web browser uses external webbrowser now - not whatever eclipse is configured for [EBZ#496487] > ------------------------------------------------------------------------------------------------------ > > Key: ERT-312 > URL: https://issues.jboss.org/browse/ERT-312 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > When selecting a port on a container, in the Docker Explorer view -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-314) Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-314?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-314: -------------------------------- Sprint: devex #116 2016/06/15 - 07/05 > Add default entry for 'Docker Hub' in the registry accounts [EBZ#496177] > ------------------------------------------------------------------------ > > Key: ERT-314 > URL: https://issues.jboss.org/browse/ERT-314 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Nick Boldt > Labels: Docker, bzira > > The registry will just contain the Server Address, so the user will have just to edit the settings to specify the credentials if he/she wants to push images. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-311) Create Container progress dialog stuck on 100% [EBZ#496380]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-311?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-311. ------------------------------- Fix Version/s: Neon.1 (4.6) Assignee: Roland Grunberg Resolution: Done Fixed upstream. Marking as closed. > Create Container progress dialog stuck on 100% [EBZ#496380] > ----------------------------------------------------------- > > Key: ERT-311 > URL: https://issues.jboss.org/browse/ERT-311 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > Created attachment 262534 > DB client settings > When I was trying to adapt guide on https://hub.docker.com/_/mariadb/ for mariadb the Progress bar is showing Create Container: (100%), but the container is running. > Steps to reproduce: > 1. Create mariadb: > Adapt command ("docker run --name some-mariadb -e MYSQL_ROOT_PASSWORD=password -d mariadb:tag") for "Run a Docker Image" wizard and run. The database should be running without issues. > 2. Connect to database with MySQL client: > Adapt command ("docker run -it --link some-mariadb:mysql --rm mariadb sh -c 'exec mysql -h*tcp address of running database* -P3306 -uroot -ppassword'") for Docker Tooling in Docker Container settings and run. The client is running and you can work with it, but progress bar still showing message: "Create Container: (100%)". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-239) PushImageCommandHandler directly references a Spotify client exception [EBZ#495249]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-239?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-239. ------------------------------- Fix Version/s: Neon.1 (4.6) Assignee: Roland Grunberg Resolution: Done Fixed upstream. See original Eclipse bug. > PushImageCommandHandler directly references a Spotify client exception [EBZ#495249] > ----------------------------------------------------------------------------------- > > Key: ERT-239 > URL: https://issues.jboss.org/browse/ERT-239 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > I think that this should not happen: the Spotify exceptions should be wrapped by the DockerConnection class and not exposed in the API. > The root cause seems to be in DockerConnection: > public void pushImage(final String name, final IRegistryAccount info, final IDockerProgressHandler handler) > throws DockerException, InterruptedException, DockerCertificateException -- 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