[JBoss JIRA] (JBDS-3853) Installer: use node-rcedit instead of resourceHacker
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3853?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3853:
--------------------------------
Fix Version/s: 10.0.0.Alpha2
> Installer: use node-rcedit instead of resourceHacker
> ----------------------------------------------------
>
> Key: JBDS-3853
> URL: https://issues.jboss.org/browse/JBDS-3853
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.0.0.Alpha2
>
>
> Installer's metadata and icon are changed by Gulp using Resource Hacker which requires that we manually pre-compile its configuration on every change in metadata (e.g. project version).
> Change it to node-rcedit module (already used by electron-packager to do the same thing for binary inside self-extracting zip)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22237) Property table is not updated when resource is selected and edited
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-22237:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.0.0.Final)
> Property table is not updated when resource is selected and edited
> ------------------------------------------------------------------
>
> Key: JBIDE-22237
> URL: https://issues.jboss.org/browse/JBIDE-22237
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.4.0.Alpha2
>
>
> When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22237) Property table is not updated when resource is selected and edited
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-22237:
----------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Property table is not updated when resource is selected and edited
> ------------------------------------------------------------------
>
> Key: JBIDE-22237
> URL: https://issues.jboss.org/browse/JBIDE-22237
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.4.0.Alpha2
>
>
> When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22237) Property table is not updated when resource is selected and edited
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-22237:
-------------------------------------
Assignee: Jeff Cantrill
> Property table is not updated when resource is selected and edited
> ------------------------------------------------------------------
>
> Key: JBIDE-22237
> URL: https://issues.jboss.org/browse/JBIDE-22237
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.0.0.Final
>
>
> When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22237) Property table is not updated when resource is selected and edited
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22237?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-22237:
----------------------------------
Fix Version/s: 4.0.0.Final
> Property table is not updated when resource is selected and edited
> ------------------------------------------------------------------
>
> Key: JBIDE-22237
> URL: https://issues.jboss.org/browse/JBIDE-22237
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.0.0.Final
>
>
> When an entry is selected in a properties tab for an openshift resource and the resources changes, you can no longer edit/update that resource until its refreshed. For example while implementing scaling, I can select a dc, scale it up, but then receive an error when I immediately try to scale it down because the resource version is out of sync.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22239:
--------------------------------
Fix Version/s: 4.4.0.Alpha2
> Allow a user to choose to permanently update their desired replicas for their deployment
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22239
> URL: https://issues.jboss.org/browse/JBIDE-22239
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff Cantrill
> Fix For: 4.4.0.Alpha2
>
>
> When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest:
> * Adding a custom dialog in the "..to.." option
> * Update to use a spinner
> * Add a checkbox to 'make the change perminent'
> * If checkbox=true, you should only need to update the dc if it has a configchange trigger.
> * Optionally show checkbox if unable to determine the dc associated with the deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-22239:
----------------------------------
Story Points: 8
> Allow a user to choose to permanently update their desired replicas for their deployment
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22239
> URL: https://issues.jboss.org/browse/JBIDE-22239
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff Cantrill
>
> When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest:
> * Adding a custom dialog in the "..to.." option
> * Update to use a spinner
> * Add a checkbox to 'make the change perminent'
> * If checkbox=true, you should only need to update the dc if it has a configchange trigger.
> * Optionally show checkbox if unable to determine the dc associated with the deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-22239:
-------------------------------------
Summary: Allow a user to choose to permanently update their desired replicas for their deployment
Key: JBIDE-22239
URL: https://issues.jboss.org/browse/JBIDE-22239
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.0.Alpha1
Reporter: Jeff Cantrill
When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest:
* Adding a custom dialog in the "..to.." option
* Update to use a spinner
* Add a checkbox to 'make the change perminent'
* If checkbox=true, you should only need to update the dc if it has a configchange trigger.
* Optionally show checkbox if unable to determine the dc associated with the deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22235) NullPointerException in BarrierProgressWaitJob.canceling
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22235?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-22235.
---------------------------------
Resolution: Done
pushed to master, simple null check.
> NullPointerException in BarrierProgressWaitJob.canceling
> --------------------------------------------------------
>
> Key: JBIDE-22235
> URL: https://issues.jboss.org/browse/JBIDE-22235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.canceling(BarrierProgressWaitJob.java:143)
> at org.eclipse.core.internal.jobs.InternalJob.cancel(InternalJob.java:185)
> at org.eclipse.core.runtime.jobs.Job.cancel(Job.java:220)
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.monitorSafeJoin(BarrierProgressWaitJob.java:135)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:330)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:319)
> at org.jboss.tools.foundation.core.ecf.internal.URLTransportCache.downloadAndCache(URLTransportCache.java:177)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:186)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:88)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:244)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadProperties(VersionPropertiesProvider.java:271)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:151)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamplesUrl(ProjectExampleJsonProvider.java:141)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamples(ProjectExampleJsonProvider.java:55)
> at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.0.1.Final-v20160401-1059-B103 |
> | org.jboss.tools.foundation.core | 1.2.1.Final-v20160408-2358-B112 | 1.2.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.project.examples | 3.0.1.Final-v20160401-1059-B103 | 3.0.1.Final-v20160401-1059-B103 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a1ed7e4b0e9dd9c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22235) NullPointerException in BarrierProgressWaitJob.canceling
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22235?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22235:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> NullPointerException in BarrierProgressWaitJob.canceling
> --------------------------------------------------------
>
> Key: JBIDE-22235
> URL: https://issues.jboss.org/browse/JBIDE-22235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.lang.NullPointerException: null
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.canceling(BarrierProgressWaitJob.java:143)
> at org.eclipse.core.internal.jobs.InternalJob.cancel(InternalJob.java:185)
> at org.eclipse.core.runtime.jobs.Job.cancel(Job.java:220)
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.monitorSafeJoin(BarrierProgressWaitJob.java:135)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:330)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.download(URLTransportUtility.java:319)
> at org.jboss.tools.foundation.core.ecf.internal.URLTransportCache.downloadAndCache(URLTransportCache.java:177)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:186)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:88)
> at org.jboss.tools.foundation.core.ecf.URLTransportUtility.getCachedFileForURL(URLTransportUtility.java:244)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadProperties(VersionPropertiesProvider.java:271)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:151)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamplesUrl(ProjectExampleJsonProvider.java:141)
> at org.jboss.tools.project.examples.internal.ProjectExampleJsonProvider.getExamples(ProjectExampleJsonProvider.java:55)
> at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.jboss.tools.central | 2.0.1.Final-v20160401-1059-B103 | 2.0.1.Final-v20160401-1059-B103 |
> | org.jboss.tools.foundation.core | 1.2.1.Final-v20160408-2358-B112 | 1.2.1.Final-v20160408-2358-B112 |
> | org.jboss.tools.project.examples | 3.0.1.Final-v20160401-1059-B103 | 3.0.1.Final-v20160401-1059-B103 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a1ed7e4b0e9dd9c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months