[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
[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
[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
[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
[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