[JBoss JIRA] (JBIDE-21966) oc rsync triggered when adding/removing breakpoints
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21966:
----------------------------------------
Summary: oc rsync triggered when adding/removing breakpoints
Key: JBIDE-21966
URL: https://issues.jboss.org/browse/JBIDE-21966
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
Assignee: Xavier Coulon
Fix For: 4.3.1.CR1
With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
AFTER | BEFORE
!http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21965) oc rsync triggered when adding/removing breakpoints
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21965?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-21965:
-------------------------------------
Assignee: Xavier Coulon
> oc rsync triggered when adding/removing breakpoints
> ---------------------------------------------------
>
> Key: JBIDE-21965
> URL: https://issues.jboss.org/browse/JBIDE-21965
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> With a server adapter set for openshift, in started mode, whenever a breakpoint is added to a class of the deployed project, rsync is triggered.
> in OpenShiftResourceChangeListener, testing the markers flag and moving the resource adding to the list up in the if block, makes it better. The downside is creating new folders doesn’t trigger new rsyncs.
> AFTER | BEFORE
> !http://content.screencast.com/users/fbricon/folders/Jing/media/45e7367b-5338-4f56-b5c2-e8ad04158633/00000375.png|width=800!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak commented on JBDS-3651:
-------------------------------------
Other things that might slow down the startup are JSPM and Babel... we might need to transpile all sources and [bundle JSPM modules|https://github.com/jspm/jspm-cli/blob/master/docs/production-work...] during build.
> Reduce the delay between the main window opening and the first page being rendered
> ----------------------------------------------------------------------------------
>
> Key: JBDS-3651
> URL: https://issues.jboss.org/browse/JBDS-3651
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 9.1.0.CR1, 9.1.0.GA
>
>
> Starting the installer right now leaves the user with about 3 seconds of staring at an empty window before the content shows up.
> I've done a few tests on this matter and it seems majority of those 3 seconds is spent on angular bootstrap - mainly loading the required files and registering controllers. Replacing the index with simple static HTML causes the page to render almost instantaneously.
> We should consider some way of showing the GUI before the user falls asleep (before angular fully loads the entire app).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21949) Allow user to turn on/off showing console when output changes
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21949?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21949:
----------------------------------
Priority: Critical (was: Major)
> Allow user to turn on/off showing console when output changes
> -------------------------------------------------------------
>
> Key: JBIDE-21949
> URL: https://issues.jboss.org/browse/JBIDE-21949
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> At the moment every publish to OpenShift via rsync show console with output from rsync (done in JBIDE-21326). User is forced to see console output. It would be nice if I could disable/enable showing console output when content changes. Something like server's console output has - toggle button Show Console Output When Standard Out Changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3711) JBDS setup is called after installation
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3711?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3711:
------------------------------
Description: What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since the JDK path is otherwise already set during the headless installation. (was: What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since it the JDK is otherwise already set during the headless installation.)
> JBDS setup is called after installation
> ---------------------------------------
>
> Key: JBDS-3711
> URL: https://issues.jboss.org/browse/JBDS-3711
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
>
> What the setup does is it replaces the -vm path for the selected/installed JDK path in jbdevstudio.ini. This should only be used when the user selects a preexisting install of JBDS, since the JDK path is otherwise already set during the headless installation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years