[JBoss JIRA] (JBDS-3573) JBDS 9.1.0.beta1 is "chatty" when the UI is opened
by Jiri Pallich (JIRA)
[ https://issues.jboss.org/browse/JBDS-3573?page=com.atlassian.jira.plugin.... ]
Jiri Pallich updated JBDS-3573:
-------------------------------
Status: New (was: New)
> JBDS 9.1.0.beta1 is "chatty" when the UI is opened
> --------------------------------------------------
>
> Key: JBDS-3573
> URL: https://issues.jboss.org/browse/JBDS-3573
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: welcome
> Affects Versions: 9.1.0.Beta1
> Environment: Version: 9.1.0.Beta1
> Build id: Beta1-v20151210-1215-B180
> Build date: 20151210-1215
> Reporter: Len DiMaggio
> Priority: Minor
>
> The following is written to stdout when the UI is opened:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [bundleresource://1068.fwk1984954272:1/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [bundleresource://1068.fwk1984954272:2/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> 14:52:13.313 [Worker-6] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml]
> 14:52:14.543 [Worker-16] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/ldimaggi/.m2/repository
> 14:52:14.552 [Worker-16] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/ldimaggi/.m2/repository
> 14:52:14.553 [Worker-16] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml]
> 14:52:14.556 [Worker-16] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21428) Server adapter: cannot publish, cannot find "oc" executable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21428?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21428:
------------------------------------------
[~scabanovich] debugging I saw that the oc binary that's found on the path is displayed but not used by the server adapter publishing method (JBIDE-21301). The server adapter is always querying the preferences which dont hold any value.
I would most likely provide a way to get the oc binary path that 1st queries preferences and then falls back to the path. I think that we dont want to store the location found on $PATH in the preferences since the content of $PATH might change. Furthermore I'd think that preferences should override $PATH.
> Server adapter: cannot publish, cannot find "oc" executable
> -----------------------------------------------------------
>
> Key: JBIDE-21428
> URL: https://issues.jboss.org/browse/JBIDE-21428
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.3.1.Beta2
>
> Attachments: could-not-sync-error.png, oc-binary-preferences.png
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21326) Server Adapter: Publishing is not telling me what it's doing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21326?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21326 at 1/8/16 8:48 AM:
------------------------------------------------------------------
[~scabanovich] +1. I'd start with console as we do for v2 to provide the full feedback of the "oc" binary, adding progress monitor updates and then a way for the user to disable/enable the console.
Having the std output of the oc binary redirected to the console most likely needs modifications in the openshift-restclient-java library.
was (Author: adietish):
[~scabanovich] +1. I'd start with console as we do for v2 to provide the full feedback of the "oc" binary, adding progress monitor updates and then a way for the user to disable/enable the console
> Server Adapter: Publishing is not telling me what it's doing
> ------------------------------------------------------------
>
> Key: JBIDE-21326
> URL: https://issues.jboss.org/browse/JBIDE-21326
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> Currently we dont tell the user what we're syncing up to the pod. We should open up a console that shows the (std) output of the "oc rsync" cmd that we're running behind the scenes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21326) Server Adapter: Publishing is not telling me what it's doing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21326?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21326:
------------------------------------------
[~scabanovich] +1. I'd start with console as we do for v2 to provide the full feedback of the "oc" binary, adding progress monitor updates and then a way for the user to disable/enable the console
> Server Adapter: Publishing is not telling me what it's doing
> ------------------------------------------------------------
>
> Key: JBIDE-21326
> URL: https://issues.jboss.org/browse/JBIDE-21326
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> Currently we dont tell the user what we're syncing up to the pod. We should open up a console that shows the (std) output of the "oc rsync" cmd that we're running behind the scenes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months