August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20424) JVMProblemDetector throws FileNotFoundException

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20424?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20424: -------------------------------------- Assignee: Daniel Azarov > JVMProblemDetector throws FileNotFoundException > ------------------------------------------------ > > Key: JBIDE-20424 > URL: https://issues.jboss.org/browse/JBIDE-20424 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.Beta2 > Environment: Linux > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.3.0.CR1 > > > This exception should not be reported, because missing file it is perfectly fine until first message to reported to log: > {code}!ENTRY org.jboss.tools.foundation.checkup 2 0 2015-08-05 15:43:32.481 > !MESSAGE /home/eskimo/Projects/jbdevstudio/4.3.x/fork/jbds-releng/.ws/junit-workspace/.metadata/.log (No such file or directory) > !STACK 0 > java.io.FileNotFoundException: /home/eskimo/Projects/jbdevstudio/4.3.x/fork/jbds-releng/.ws/junit-workspace/.metadata/.log (No such file or directory) > at java.io.RandomAccessFile.open0(Native Method) > at java.io.RandomAccessFile.open(RandomAccessFile.java:316) > at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243) > at org.eclipse.ui.internal.views.log.TailInputStream.<init>(TailInputStream.java:24) > at org.jboss.tools.foundation.checkup.JVMProblemDetector.earlyStartup(JVMProblemDetector.java:108) > at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:90) > at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:68) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2812) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20424) JVMProblemDetector throws FileNotFoundException

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-20424: ------------------------------------- Summary: JVMProblemDetector throws FileNotFoundException Key: JBIDE-20424 URL: https://issues.jboss.org/browse/JBIDE-20424 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.3.0.Beta2 Environment: Linux Reporter: Denis Golovin This exception should not be reported, because missing file it is perfectly fine until first message to reported to log: {code}!ENTRY org.jboss.tools.foundation.checkup 2 0 2015-08-05 15:43:32.481 !MESSAGE /home/eskimo/Projects/jbdevstudio/4.3.x/fork/jbds-releng/.ws/junit-workspace/.metadata/.log (No such file or directory) !STACK 0 java.io.FileNotFoundException: /home/eskimo/Projects/jbdevstudio/4.3.x/fork/jbds-releng/.ws/junit-workspace/.metadata/.log (No such file or directory) at java.io.RandomAccessFile.open0(Native Method) at java.io.RandomAccessFile.open(RandomAccessFile.java:316) at java.io.RandomAccessFile.<init>(RandomAccessFile.java:243) at org.eclipse.ui.internal.views.log.TailInputStream.<init>(TailInputStream.java:24) at org.jboss.tools.foundation.checkup.JVMProblemDetector.earlyStartup(JVMProblemDetector.java:108) at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:90) at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:68) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2812) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20167) Openshift Tooling Usage Tracking

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20167?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20167: ------------------------------------- Attachment: import_app_v2.png > Openshift Tooling Usage Tracking > -------------------------------- > > Key: JBIDE-20167 > URL: https://issues.jboss.org/browse/JBIDE-20167 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Labels: usage > Fix For: 4.3.0.CR1 > > Attachments: import_app_v2.png > > > Embed usage tracking logic in the Openshift v3 tooling - allowing us to know how many individuals are using those tools. > Usage API docs are here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/api/usage/usa... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20167) Openshift Tooling Usage Tracking

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20167?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20167: ------------------------------------------ I added separate events for creating and importing applications from v3 or v2 hosts.: !import_app_v2.png! * new_app_v2 * import_app_v2 * new_app_v3 * import_app_v3 > Openshift Tooling Usage Tracking > -------------------------------- > > Key: JBIDE-20167 > URL: https://issues.jboss.org/browse/JBIDE-20167 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Labels: usage > Fix For: 4.3.0.CR1 > > > Embed usage tracking logic in the Openshift v3 tooling - allowing us to know how many individuals are using those tools. > Usage API docs are here: https://github.com/jbosstools/jbosstools-devdoc/blob/master/api/usage/usa... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19764) Remove JARs from seam test projects

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19764?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-19764: --------------------------------------------- Assignee: Viacheslav Kabanovich (was: Alexey Kazakov) > Remove JARs from seam test projects > ----------------------------------- > > Key: JBIDE-19764 > URL: https://issues.jboss.org/browse/JBIDE-19764 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: seam2 > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20423) Docker explorer - "Remove Containers" option is disabled in 4.3.0.Beta2

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-20423: ------------------------------------ Summary: Docker explorer - "Remove Containers" option is disabled in 4.3.0.Beta2 Key: JBIDE-20423 URL: https://issues.jboss.org/browse/JBIDE-20423 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Affects Versions: 4.3.0.Beta2 Environment: RHEL7 Java8 Reporter: Len DiMaggio Will the option be enabled for GA? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20422) Docker explorer - Stopping a container removes it from the explorer display

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20422?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-20422: --------------------------------- Description: Once the container is removed from the Docker explorer, the user must go to the CLI to restart it and have it appear again in the explorer. Why not leave it visible in the Docker explorer and mark it as stopped? was: Once the container is removed from the Docker explorer, the user must go to the CLI to restart it. Why not leave it visible in the Docker explorer and mark it as stopped? > Docker explorer - Stopping a container removes it from the explorer display > --------------------------------------------------------------------------- > > Key: JBIDE-20422 > URL: https://issues.jboss.org/browse/JBIDE-20422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Environment: RHEL 7 > Java 8 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > > Once the container is removed from the Docker explorer, the user must go to the CLI to restart it and have it appear again in the explorer. > Why not leave it visible in the Docker explorer and mark it as stopped? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20422) Docker explorer - Stopping a container removes it from the explorer display

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20422?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20422: ----------------------------------- Assignee: Xavier Coulon > Docker explorer - Stopping a container removes it from the explorer display > --------------------------------------------------------------------------- > > Key: JBIDE-20422 > URL: https://issues.jboss.org/browse/JBIDE-20422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Beta2 > Environment: RHEL 7 > Java 8 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > > Once the container is removed from the Docker explorer, the user must go to the CLI to restart it. > Why not leave it visible in the Docker explorer and mark it as stopped? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20422) Docker explorer - Stopping a container removes it from the explorer display

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20422?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20422: -------------------------------- Component/s: upstream > Docker explorer - Stopping a container removes it from the explorer display > --------------------------------------------------------------------------- > > Key: JBIDE-20422 > URL: https://issues.jboss.org/browse/JBIDE-20422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker, upstream > Affects Versions: 4.3.0.Beta2 > Environment: RHEL 7 > Java 8 > Reporter: Len DiMaggio > Assignee: Xavier Coulon > > Once the container is removed from the Docker explorer, the user must go to the CLI to restart it. > Why not leave it visible in the Docker explorer and mark it as stopped? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20422) Docker explorer - Stopping a container removes it from the explorer display

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-20422: ------------------------------------ Summary: Docker explorer - Stopping a container removes it from the explorer display Key: JBIDE-20422 URL: https://issues.jboss.org/browse/JBIDE-20422 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: docker Affects Versions: 4.3.0.Beta2 Environment: RHEL 7 Java 8 Reporter: Len DiMaggio Once the container is removed from the Docker explorer, the user must go to the CLI to restart it. Why not leave it visible in the Docker explorer and mark it as stopped? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015