[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened
by Jan Richter (JIRA)
Jan Richter created JBDS-3696:
---------------------------------
Summary: Browse buttons should not respond when a file dialog is opened
Key: JBDS-3696
URL: https://issues.jboss.org/browse/JBDS-3696
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued to open once the current one closes. We should not allow this kind of chaining - it is fairly annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21920:
----------------------------------
Description:
After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding . Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
But when using port forwading, there is an error with following stack
{code}
com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189)
at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123)
at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66)
at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128)
at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124)
at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110)
at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
was:
After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding (wizard is opened but starting throws an error with message as seen below). Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
> Cannot use features which are using oc binary
> ---------------------------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding . Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
> But when using port forwading, there is an error with following stack
> {code}
> com.openshift.restclient.capability.resources.LocationNotFoundException: The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.getOpenShiftBinaryLocation(AbstractOpenShiftBinaryCapability.java:189)
> at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:123)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:66)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:128)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
> at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:124)
> at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.startPortForwarding(PortForwardingWizardModel.java:110)
> at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardPage$3$1.run(PortForwardingWizardPage.java:157)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21920:
----------------------------------
Summary: Cannot use features which are using oc binary (was: Cannot show logs from pods)
> Cannot use features which are using oc binary
> ---------------------------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds). Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21920:
----------------------------------
Description:
After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding (wizard is opened but starting throws an error with message as seen below). Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
was:
After latest update of nightly JBT I am not able to get logs from pods(/builds). Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
> Cannot use features which are using oc binary
> ---------------------------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds) or use port forwarding (wizard is opened but starting throws an error with message as seen below). Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot show logs from pods
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21920:
----------------------------------
Description:
After latest update of nightly JBT I am not able to get logs from pods(/builds). Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
was:
After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
{code}
The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
{code}
There is no stack trace available for this error in error log.
> Cannot show logs from pods
> --------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds). Because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot show logs from pods
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21920:
----------------------------------
Summary: Cannot show logs from pods (was: Cannot use features which are using oc binary)
> Cannot show logs from pods
> --------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3695?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3695:
------------------------------------
Is this successful if the user runs the installer as an admin user?
> Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
> ------------------------------------------------------------------------------------------
>
> Key: JBDS-3695
> URL: https://issues.jboss.org/browse/JBDS-3695
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Labels: havoc
>
> So if the user selects an existing JBDS installation from their Program Files folder and lets us install JDK, the installation will fail when the installer tries to change jbdevstudio.ini to point to the JDK we installed.
> The problem once again is in windows magic, it does not allow to modify files in a protected folder without administrative rights.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21835) Server adapter: incremental deployment is broken
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21835?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21835:
---------------------------------------
Well what I consider(ed) as an issue is that once OpenShift server adapter is created, it redeployes application. But once server adapter is created and running, changes to code are incrementally deployed. [~fbricon] [~rob.stryker] if you consider that redeploying after creation of new OpenShift 3 server adapter is ok and good enough, mark this issue as resolved please.
> Server adapter: incremental deployment is broken
> ------------------------------------------------
>
> Key: JBIDE-21835
> URL: https://issues.jboss.org/browse/JBIDE-21835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master...
> Deploy an eap basic app on openshift,
> import the kitchensink code in the workspace
> wait for the application to deploy and run on openshift
> Issue #1
> - when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project.
> - After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to
> Issue #2
> - create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard
> - jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink
> - local change is not pushed immediately to the server. module restart happens before the change is effective.
> (Fred indicates this issue was not replicatable on most recent test)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3695) Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
by Jan Richter (JIRA)
Jan Richter created JBDS-3695:
---------------------------------
Summary: Using existing JBDS with downloaded/installed JDK fails if JBDS is in Program Files folder
Key: JBDS-3695
URL: https://issues.jboss.org/browse/JBDS-3695
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
So if the user selects an existing JBDS installation from their Program Files folder and lets us install JDK, the installation will fail when the installer tries to change jbdevstudio.ini to point to the JDK we installed.
The problem once again is in windows magic, it does not allow to modify files in a protected folder without administrative rights.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years