[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ]
Jan Richter reassigned JBDS-3769:
---------------------------------
Assignee: Jan Richter
> Remove JSPM from dependencies
> -----------------------------
>
> Key: JBDS-3769
> URL: https://issues.jboss.org/browse/JBDS-3769
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Jan Richter
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.1.AM2
>
>
> After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
> Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3651:
-----------------------------------
The main subtasks are tracked in the following issues:
* Remove JSPM from dependencies: JBDS-3769
* Transpile code at build time instead of run time: JBDS-3958
After these tasks are done, hopefully the initial load time will be improved drastically.
> 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: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.0.1.AM2
>
>
> 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)
9 years, 6 months
[JBoss JIRA] (JBDS-3958) Transpile code at build time instead of run time
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3958?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3958:
------------------------------
Description:
The major slowing factor in the initial load time is babel transpiling the code when the application starts (currently run as jspm subroutine).
Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
was:
The major slowing factor in the initial load time is babel transpiling the code at when the application starts (currently run as jspm subroutine).
Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
> Transpile code at build time instead of run time
> ------------------------------------------------
>
> Key: JBDS-3958
> URL: https://issues.jboss.org/browse/JBDS-3958
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Jan Richter
>
> The major slowing factor in the initial load time is babel transpiling the code when the application starts (currently run as jspm subroutine).
> Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3958) Transpile code at build time instead of run time
by Jan Richter (JIRA)
Jan Richter created JBDS-3958:
---------------------------------
Summary: Transpile code at build time instead of run time
Key: JBDS-3958
URL: https://issues.jboss.org/browse/JBDS-3958
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: platform-installer
Affects Versions: 10.0.0.GA
Reporter: Jan Richter
Assignee: Jan Richter
The major slowing factor in the initial load time is babel transpiling the code at when the application starts (currently run as jspm subroutine).
Once JSPM is removed (JBDS-3769), we need to ensure that babel is not used as a production dependency anymore. For that we need to put the transpiling step before the build (generate) step.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3769) Remove JSPM from dependencies
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3769?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3769:
------------------------------
Fix Version/s: 10.0.1.AM2
(was: 10.0.1.AM1)
> Remove JSPM from dependencies
> -----------------------------
>
> Key: JBDS-3769
> URL: https://issues.jboss.org/browse/JBDS-3769
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Priority: Critical
> Labels: havoc
> Fix For: 10.0.1.AM2
>
>
> After a change introduced in jspm 0.16.32 which caused our builds to fail (JBDS-3747) now another issue has arisen causing errors on npm install (both local and in CI environment). Even if this new issue is fixed in jspm, we would still have to face the first issue after updating.
> Therefore I propose to remove jspm entirely. We only use a small fraction of its functionality and it needlessly complicates the build + causes major issues. Since such change is likely to be quite complex, we should slip it after the April release and use an existing quick fix in the mean time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3651:
------------------------------
Fix Version/s: 10.0.1.AM2
(was: 10.0.1.AM1)
> 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: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.0.1.AM2
>
>
> 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)
9 years, 6 months
[JBoss JIRA] (JBIDE-22679) Run integration-test against source (rather than package)
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22679?page=com.atlassian.jira.plugi... ]
Rastislav Wagner commented on JBIDE-22679:
------------------------------------------
So I have devstudio.feature and cdi.feature defined
{code}
<requirement>
<type>p2-installable-unit</type>
<id>com.jboss.devstudio.core.feature.feature.group</id>
<versionRange>0.0.0</versionRange>
</requirement>
<requirement>
<type>p2-installable-unit</type>
<id>org.jboss.tools.cdi.feature.feature.group</id>
<versionRange>0.0.0</versionRange>
</requirement>
{code}
It runs devstudio (which is OK) but somehow ignores my locally build CDI (log doesn't say anything) and uses the one from devstudio feature. My locally built cdi has higher timestamp than the one in devstudio.
> Run integration-test against source (rather than package)
> ---------------------------------------------------------
>
> Key: JBIDE-22679
> URL: https://issues.jboss.org/browse/JBIDE-22679
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build, qa
> Reporter: Mickael Istria
> Assignee: Rastislav Wagner
>
> Currently, integration-tests run against a prepared package (of Developer Studio). In order to more easily run those tests locally or as part of the development process, it would be nice to also have them running directly against source code of the component.
> Tycho provide a mechanism to provision the application under test according to existing definition: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t... , or maybe even by simply making Developer Studio part of the test target-platform and define it as the application/produce under test: https://eclipse.org/tycho/sitedocs/tycho-surefire/tycho-surefire-plugin/t...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22603 at 7/1/16 6:46 AM:
---------------------------------------------------------------
Well, this is something what should be fixed ASAP. I am not even able to publish project (I have to try do it several times, blocking jobs), nor start debugging (this I can't get working at all because of waiting for a pod). It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate.
was (Author: mlabuda):
Well, this is something what should be fixed ASAP. I am not even able to publish project, nor start debugging because of those WatchManager jobs. It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate.
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-22603 at 7/1/16 6:43 AM:
---------------------------------------------------------------
Well, this is something what should be fixed ASAP. I am not even able to publish project, nor start debugging because of those WatchManager jobs. It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate.
was (Author: mlabuda):
Well, this is something what should get be fixed ASAP. I am not even able to publish project, nor start debugging because of those WatchManager jobs. It makes CDK OpenShift unusable for me. But I am not sure why I am able to reproduce this at 100 % success rate.
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: explorer, openshift_v3
> Fix For: 4.4.x
>
> Attachments: watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months