April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3739: --------------------------------- Target Release: 9.1.0.GA > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Hardy Ferentschik > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22176) [thym] Implement Engines Management in config.xml editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22176?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22176: -------------------------------------- Assignee: Gorkem Ercan > [thym] Implement Engines Management in config.xml editor > -------------------------------------------------------- > > Key: JBIDE-22176 > URL: https://issues.jboss.org/browse/JBIDE-22176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.4.0.Alpha1 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491580 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016