[JBoss JIRA] (JBIDE-21969) Show in Browser: route chooser should allow to user to choose route permanently
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21969?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21969:
------------------------------------------
merged into master
> Show in Browser: route chooser should allow to user to choose route permanently
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21969
> URL: https://issues.jboss.org/browse/JBIDE-21969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.0.Alpha1
>
> Attachments: route-chooser.png
>
>
> steps to reproduce:
> # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
> # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
> # EXEC: launch New OpenShift 3 Server Adapter wizard
> # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
> # EXEC: create the adapter by picking service, local project etc.
> # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
> # ASSERT: Route chooser shows up (since there are several routes available)
> Result:
> There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
> !route-chooser.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21993) Show in Browser: route chooser should allow to user to choose route permanently
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21993?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21993:
------------------------------------------
cherry-picked to jbosstools-4.3.x
> Show in Browser: route chooser should allow to user to choose route permanently
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21993
> URL: https://issues.jboss.org/browse/JBIDE-21993
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: route-chooser.png
>
>
> steps to reproduce:
> # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
> # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
> # EXEC: launch New OpenShift 3 Server Adapter wizard
> # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
> # EXEC: create the adapter by picking service, local project etc.
> # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
> # ASSERT: Route chooser shows up (since there are several routes available)
> Result:
> There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
> !route-chooser.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21993) Show in Browser: route chooser should allow to user to choose route permanently
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21993:
----------------------------------------
Summary: Show in Browser: route chooser should allow to user to choose route permanently
Key: JBIDE-21993
URL: https://issues.jboss.org/browse/JBIDE-21993
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Andre Dietisheim
Assignee: Viacheslav Kabanovich
Fix For: 4.4.0.Alpha1
steps to reproduce:
# ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
# ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
# EXEC: launch New OpenShift 3 Server Adapter wizard
# ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
# EXEC: create the adapter by picking service, local project etc.
# EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
# ASSERT: Route chooser shows up (since there are several routes available)
Result:
There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
!route-chooser.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21993) Show in Browser: route chooser should allow to user to choose route permanently
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21993?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21993:
-------------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.4.0.Alpha1)
> Show in Browser: route chooser should allow to user to choose route permanently
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21993
> URL: https://issues.jboss.org/browse/JBIDE-21993
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
> Attachments: route-chooser.png
>
>
> steps to reproduce:
> # ASSERT: have an apps with service and route running on OpenShift. Have it imported to your workspace
> # ASSERT: you need at least a 2nd route in the same project (ex. by having a 2nd app in the same project)
> # EXEC: launch New OpenShift 3 Server Adapter wizard
> # ASSERT: make sure that you have *Prompt for route when multiple routes available to show in browser* checked (no route permanently selected)
> # EXEC: create the adapter by picking service, local project etc.
> # EXEC: in the context menu of your new server adapter: pick Show In > Web Browser
> # ASSERT: Route chooser shows up (since there are several routes available)
> Result:
> There's no way to permanently choose a route. The route chooser will always show up (as long as I have several routes in the same project)
> !route-chooser.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21981) Error during rsync
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21981:
---------------------------------------
The proposed patch fixes the {{stream is closed}} part of this issue, but the underlying file permissions part remains.
[~rob.stryker] [~fbricon]: after a bit of investigation, I found that the tooling was trying to rename a temporary {{<workspace>/.metadata/.plugins/org.eclipse.wst.server.core/tmp9098154414}} file
into
{{<workspace>/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war/META-INF/MANIFEST.MF}}
but
{{<workspace>/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war}}
is a _file_, not a directory on my system. Maybe because the application was deployed in a non-exploded form before ?
> Error during rsync
> ------------------
>
> Key: JBIDE-21981
> URL: https://issues.jboss.org/browse/JBIDE-21981
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> While testing the debugging support on the server adapter, I got the following error:
> {code}
> Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy
> OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66)
> rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9]
> error: exit status 23
> {code}
> The content of the {{.../deploy}} directory was:
> {code}
> drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./
> drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../
> -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt
> drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/
> -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed
> -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying
> -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar
> -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed
> -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying
> {code}
> As a side note, displaying the content of the process error message in the MessageDialog triggers an error later:
> {code}
> [ERROR] 2016-03-25 12:19:53,006 com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync - Could not retrieve error message from process
> java.io.IOException: Stream closed
> at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:336)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at java.io.Reader.read(Reader.java:140)
> at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1485)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1461)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1408)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:1433)
> at org.apache.commons.io.IOUtils.toString(IOUtils.java:585)
> at org.apache.commons.io.IOUtils.toString(IOUtils.java:563)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.getErrorMessage(OpenShiftBinaryRSync.java:107)
> at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryRSync.await(OpenShiftBinaryRSync.java:94)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21984) Wrong Source Path when creating OS3 Server Adapter for multiple applications
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21984?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21984:
-------------------------------------
Labels: openshift_v3 server_adapter_wizard (was: )
> Wrong Source Path when creating OS3 Server Adapter for multiple applications
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21984
> URL: https://issues.jboss.org/browse/JBIDE-21984
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: launch_config.png, server-adapter.png
>
>
> 1.
> !server-adapter.png|thumbnail!
> 2. Even selecting the correct source manually doesn't help. The eclipse project is still incorrect in the launch config.
> !launch_config.png|thumbnail!
> Maybe it's because the nodejs eclipse project is not a wtp project and the server adapter picks up the only available wtp module - eap-app.
> The only way to create a proper server adapter for the nodejs-example is to delete the eap eclipse project from the workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3663) Use URL redirects for vagrant and VirtualBox
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/JBDS-3663?page=com.atlassian.jira.plugin.... ]
Pavol Pitonak edited comment on JBDS-3663 at 3/29/16 8:48 AM:
--------------------------------------------------------------
[~dgolovin], why did you change requirements.json in installer to bundle VirtualBox?
# if you want to bundle a dependency, bundle should be set to *yes*
# AFAIK we can't bundle VirtualBox
# why are we using http link and not https?
was (Author: ppitonak):
[~dgolovin], why did you change requirements.json in installer to bundle VirtualBox?
# if you want to bundle a dependency, bundle should be set to *yes*
# AFAIK we can't bundle VirtualBox
> Use URL redirects for vagrant and VirtualBox
> --------------------------------------------
>
> Key: JBDS-3663
> URL: https://issues.jboss.org/browse/JBDS-3663
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Pete Muir
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> In case the third parties change their download locations, we should use URL redirects, and not directly embed the download URLs in to our downloader
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21992) Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21992?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21992:
-------------------------------------
Description:
The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
!deploy-config-scalability-page.png!
was:
The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix:
!deploy-config-scalability-page.png!
> Deploy Docker Image wizard: "Deployment Configuration & Scalability" page has minor UI issues
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21992
> URL: https://issues.jboss.org/browse/JBIDE-21992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: deploy-config-scalability-page.png
>
>
> The ""Deployment Configuration & Scalability" wizard page when deploying a docker image has minor UI glitches that we should fix as you can see in the following screenshot. We should also maybe use 3 groups to distinguish the 3 settings cathegories in more obvious way.
> !deploy-config-scalability-page.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years