[JBoss JIRA] (JBIDE-22174) Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22174?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22174:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22174
> URL: https://issues.jboss.org/browse/JBIDE-22174
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> When opening Deploy Image to OpenShift wizard via context menu of a docker image in Docker Explorer, selected project (or a connection if no project under a connection is selected) should be selected in combo in the wizard. At the moment, if there is precisely 1 connection, it is selected (if there are more connections, no connection is selected and following steps is not reachable) and if there is precisely 1 project, that one is selected (if there are more projects, no project is selected). This could be refined a bit. In case of selection would be the selected one in combo. In case of existence of more connections/projects and no selection, maybe the first one listed could be selected (but this is probably personal preference, maybe it is not a good idea).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22174) Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22174?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22174:
-----------------------------------
Assignee: Viacheslav Kabanovich
> Deploy Image to OpenShift wizard could respect selected connection and project from OpenShift Explorer
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22174
> URL: https://issues.jboss.org/browse/JBIDE-22174
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> When opening Deploy Image to OpenShift wizard via context menu of a docker image in Docker Explorer, selected project (or a connection if no project under a connection is selected) should be selected in combo in the wizard. At the moment, if there is precisely 1 connection, it is selected (if there are more connections, no connection is selected and following steps is not reachable) and if there is precisely 1 project, that one is selected (if there are more projects, no project is selected). This could be refined a bit. In case of selection would be the selected one in combo. In case of existence of more connections/projects and no selection, maybe the first one listed could be selected (but this is probably personal preference, maybe it is not a good idea).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3434:
------------------------------
Fix Version/s: 10.x
(was: 9.x)
> Kubernetes editor & wizard
> --------------------------
>
> Key: JBDS-3434
> URL: https://issues.jboss.org/browse/JBDS-3434
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 8.x
> Reporter: Charles Moulliard
> Assignee: Max Rydahl Andersen
> Fix For: 10.x
>
>
> To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose :
> - a kubernetes editor within JBDS to update the YAML or JSON file and
> - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3820) Run the msi installers with suppressed UI
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3820?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3820:
------------------------------
Affects Version/s: 9.1.0.CR1
(was: 9.1.0.GA)
> Run the msi installers with suppressed UI
> -----------------------------------------
>
> Key: JBDS-3820
> URL: https://issues.jboss.org/browse/JBDS-3820
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
>
> If I remember correctly, we've been running the msi installers with reduced UI (/qb) because suppressing the UI required administrative privileges.
> Since the 7zipped installer needs those privileges to start, we could switch to using suppressed UI (/qn), could we not?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3826) JBDS installation fails with folder name containing non-standard characters
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3826?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3826:
------------------------------
Affects Version/s: 9.1.0.CR1
(was: 9.1.0.GA)
> JBDS installation fails with folder name containing non-standard characters
> ---------------------------------------------------------------------------
>
> Key: JBDS-3826
> URL: https://issues.jboss.org/browse/JBDS-3826
> 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
>
> I have tried installing into this folder:
> {noformat}c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform{noformat}
> And JBDS installation failed immediately, the install.log was not very helpful.
> {noformat}Fri, 15 Apr 2016 11:49:50 GMT-INFO: jbds - Execute c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true,-jar,C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar,C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml
> Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds - Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml
> Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds -
> Fri, 15 Apr 2016 11:49:52 GMT-ERROR: jbds failed to install: Error: Command failed: c:\Developer~~!@#$@#@++ŇNˇaˇAsdďf¨¨°Platform\jdk8\bin\java.exe -DTRACE=true -jar C:\Users\jbossqa\AppData\Local\Temp\7zS7105.tmp\jbds.jar C:\Users\jbossqa\AppData\Local\Temp\jbds-autoinstall.xml
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3827) JBDS installation fails when (windows) user has non-ascii chars in the name
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3827?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3827:
------------------------------
Affects Version/s: 9.1.0.CR1
(was: 9.1.0.GA)
> JBDS installation fails when (windows) user has non-ascii chars in the name
> ---------------------------------------------------------------------------
>
> Key: JBDS-3827
> URL: https://issues.jboss.org/browse/JBDS-3827
> 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
>
> I have created a user named Pakoň and tried to install everything into the default folder. JBDS failed with:
> {noformat}Fri, 15 Apr 2016 12:38:40 GMT-ERROR: jbds - Error: Command failed: c:\DeveloperPlatform\jdk8\bin\java.exe -DTRACE=true -jar C:\WINDOWS\7zS9F06.tmp\jbds.jar C:\Users\Pakoň\AppData\Local\Temp\jbds-autoinstall.xml
> - ERROR -
> java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified)
> java.io.FileNotFoundException: C:\Users\Pakon\AppData\Local\Temp\jbds-autoinstall.xml (The system cannot find the path specified)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.<init>(FileInputStream.java:138)
> at com.izforge.izpack.installer.AutomatedInstaller.getXMLData(AutomatedInstaller.java:564)
> at com.izforge.izpack.installer.AutomatedInstaller.<init>(AutomatedInstaller.java:86)
> at com.izforge.izpack.installer.Installer.main(Unknown Source){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3828) Virtualbox fails to install when user has non-ascii characters in the name
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3828?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-3828:
------------------------------
Affects Version/s: 9.1.0.CR1
(was: 9.1.0.GA)
> Virtualbox fails to install when user has non-ascii characters in the name
> --------------------------------------------------------------------------
>
> Key: JBDS-3828
> URL: https://issues.jboss.org/browse/JBDS-3828
> 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
> Attachments: vbox.png
>
>
> Username: Pakoň
> Leave everything on default.
> While installing, virtualbox shows a pop-up saying
> {noformat}
> Source file not found:
> C:\Users\Pakoň\AppData\Local\Temp\common.cab.
> Verify that the file exists and that you an access it
> {noformat}
> Retry does nothing but show the dialog again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years