[JBoss JIRA] (JBDS-3789) Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3789?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3789.
----------------------------------
Resolution: Done
> Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3789
> URL: https://issues.jboss.org/browse/JBDS-3789
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, install_fail.png, log, vagrant.log, vbox.log
>
>
> This issue is being seen with the Setup-bundled-0.0.2-20160411-98 installer
> After an apparently clean/successful install, starting the CDK runtime as a server fails with this error:
> Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments
> Log files and screenshot are attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3789) Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3789?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3789:
--------------------------------------
Yes. Fixed by updating CDK - JBDS-3638
> Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3789
> URL: https://issues.jboss.org/browse/JBDS-3789
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, install_fail.png, log, vagrant.log, vbox.log
>
>
> This issue is being seen with the Setup-bundled-0.0.2-20160411-98 installer
> After an apparently clean/successful install, starting the CDK runtime as a server fails with this error:
> Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments
> Log files and screenshot are attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3804) Installer: exe distribution has wrong metadata
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3804?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3804:
-----------------------------
> Installer: exe distribution has wrong metadata
> ----------------------------------------------
>
> Key: JBDS-3804
> URL: https://issues.jboss.org/browse/JBDS-3804
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 9.1.0.GA
>
> Attachments: installer_metadata.png
>
>
> # download distribution from http://machydra.tpb.lab.eng.brq.redhat.com:8080/view/Developer%20Tooling/... (link to smaller version, bundled installer has the same problem)
> # right-click on downloaded exe file, select _Properties_, switch to _Details_ tab
> OR
> # clone git repo
> # npm install
> # npm run package-simple
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64/DeveloperPlatformInstaller.exe_ and select _Properties_, switch to _Details_ tab
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64-0.0.2.exe_ and select _Properties_, switch to _Details_ tab
> result:
> * electron-generate creates exe with correct metadata
> * distribution exe contains wrong metadata (e.g. copyright to Igor Pavlov)
> * *needs to be fixed before we sign the binary*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3804) Installer: exe distribution has wrong metadata
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3804?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3804:
--------------------------------
> Installer: exe distribution has wrong metadata
> ----------------------------------------------
>
> Key: JBDS-3804
> URL: https://issues.jboss.org/browse/JBDS-3804
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 9.1.0.GA
>
> Attachments: installer_metadata.png
>
>
> # download distribution from http://machydra.tpb.lab.eng.brq.redhat.com:8080/view/Developer%20Tooling/... (link to smaller version, bundled installer has the same problem)
> # right-click on downloaded exe file, select _Properties_, switch to _Details_ tab
> OR
> # clone git repo
> # npm install
> # npm run package-simple
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64/DeveloperPlatformInstaller.exe_ and select _Properties_, switch to _Details_ tab
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64-0.0.2.exe_ and select _Properties_, switch to _Details_ tab
> result:
> * electron-generate creates exe with correct metadata
> * distribution exe contains wrong metadata (e.g. copyright to Igor Pavlov)
> * *needs to be fixed before we sign the binary*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3804) Installer: exe distribution has wrong metadata
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3804?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3804:
---------------------------------
Target Release: 9.1.0.GA
> Installer: exe distribution has wrong metadata
> ----------------------------------------------
>
> Key: JBDS-3804
> URL: https://issues.jboss.org/browse/JBDS-3804
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Pavol Pitonak
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 9.1.0.GA
>
> Attachments: installer_metadata.png
>
>
> # download distribution from http://machydra.tpb.lab.eng.brq.redhat.com:8080/view/Developer%20Tooling/... (link to smaller version, bundled installer has the same problem)
> # right-click on downloaded exe file, select _Properties_, switch to _Details_ tab
> OR
> # clone git repo
> # npm install
> # npm run package-simple
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64/DeveloperPlatformInstaller.exe_ and select _Properties_, switch to _Details_ tab
> # right-click on _dist/win/DeveloperPlatformInstaller-win32-x64-0.0.2.exe_ and select _Properties_, switch to _Details_ tab
> result:
> * electron-generate creates exe with correct metadata
> * distribution exe contains wrong metadata (e.g. copyright to Igor Pavlov)
> * *needs to be fixed before we sign the binary*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3729) Wrong installer icon and metadata
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3729?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov closed JBDS-3729.
--------------------------------
Fix Version/s: 9.1.0.GA
Assignee: Denis Golovin
Resolution: Duplicate Issue
> Wrong installer icon and metadata
> ---------------------------------
>
> Key: JBDS-3729
> URL: https://issues.jboss.org/browse/JBDS-3729
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Hardy Ferentschik
> Assignee: Denis Golovin
> Fix For: 9.1.0.GA
>
> Attachments: installer-icon.png, installer-meta.png
>
>
> The installer icon needs styling and the meta information needs to be set properly. See _FileDescription_ and _Company_ in attached screenshot. Also the name of the installer should be adjusted - _Setup-bundled-0.0.2-20160324-_ - it should be the proper product name + a simple version string.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22175:
--------------------------------------
Assignee: Victor Rubezhny (was: Alexey Kazakov)
Looks like an upstream issue. [~vrubezhny] please take a look.
> Warnings in JBDS after importing kitchensink-jsp quickstart
> -----------------------------------------------------------
>
> Key: JBIDE-22175
> URL: https://issues.jboss.org/browse/JBIDE-22175
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Reporter: Sande Gilda
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha1
>
>
> After importing the quickstart into JBDS, the following warnings are produced
> * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path
> * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22175:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
> Warnings in JBDS after importing kitchensink-jsp quickstart
> -----------------------------------------------------------
>
> Key: JBIDE-22175
> URL: https://issues.jboss.org/browse/JBIDE-22175
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Reporter: Sande Gilda
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha1
>
>
> After importing the quickstart into JBDS, the following warnings are produced
> * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path
> * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years