June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22443: ----------------------------------- Fix Version/s: 4.4.x > Add to TP build a check that produced TP can be installed in target Eclipse version > ----------------------------------------------------------------------------------- > > Key: JBIDE-22443 > URL: https://issues.jboss.org/browse/JBIDE-22443 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform > Reporter: Mickael Istria > Fix For: 4.4.x > > > Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests. > This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible. > Technical notes: > * Trying to install all IUs from the release train site + our TP seems easier to implement > * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3794) Installer - We should document the uninstall steps

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3794?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3794. ----------------------------- The uninstall steps are unliely to change in this release, so I'm closing this isseu as finished. > Installer - We should document the uninstall steps > -------------------------------------------------- > > Key: JBDS-3794 > URL: https://issues.jboss.org/browse/JBDS-3794 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: documentation, platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 10.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3696. ----------------------------- This was fixes as part of JBDS-3788 I believe. Closing this issue as well. > Browse buttons should not respond when a file dialog is opened > -------------------------------------------------------------- > > Key: JBDS-3696 > URL: https://issues.jboss.org/browse/JBDS-3696 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc, ui > Fix For: 10.0.0.GA > > > 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 up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3653. ----------------------------- Sadly, the implemented workaround is about all we can do. And it seems to work this way, so closing. > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 10.0.0.GA > > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22195: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha2) > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.x > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=493328 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3526) Better Docker Integration

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3526?page=com.atlassian.jira.plugin.... ] Xavier Coulon updated JBDS-3526: -------------------------------- Fix Version/s: 10.x (was: 10.0.0.GA) > Better Docker Integration > -------------------------- > > Key: JBDS-3526 > URL: https://issues.jboss.org/browse/JBDS-3526 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: docker > Affects Versions: 9.0.0.GA > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 10.x > > > This is a follow-up of JBDS-3317 and JBDS-3258 to collect all the remaining features that were not implemented: > - API for server tooling > - Support for build options (https://bugs.eclipse.org/bugs/show_bug.cgi?id=474196) > - Support for .dockerignore file (https://bugs.eclipse.org/bugs/show_bug.cgi?id=469819)) > - Show ports, environment variables and links in the UI (https://bugs.eclipse.org/bugs/show_bug.cgi?id=471666) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22510) Unable to display tags for jboss/wildfly Docker image

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22510?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22510: ---------------------------------- Fix Version/s: 4.4.0.Final > Unable to display tags for jboss/wildfly Docker image > ----------------------------------------------------- > > Key: JBIDE-22510 > URL: https://issues.jboss.org/browse/JBIDE-22510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Final > > > This is reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=495338 > In the mean time, we should disable the {{DockerHubRegistryTest}} tests to avoid the build failures on Jenkins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22510) Unable to display tags for jboss/wildfly Docker image

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22510?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-22510. ----------------------------------- Resolution: Done > Unable to display tags for jboss/wildfly Docker image > ----------------------------------------------------- > > Key: JBIDE-22510 > URL: https://issues.jboss.org/browse/JBIDE-22510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Final > > > This is reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=495338 > In the mean time, we should disable the {{DockerHubRegistryTest}} tests to avoid the build failures on Jenkins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22510) Unable to display tags for jboss/wildfly Docker image

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22510?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-22510. ----------------------------------- Resolution: Cannot Reproduce Bug > Unable to display tags for jboss/wildfly Docker image > ----------------------------------------------------- > > Key: JBIDE-22510 > URL: https://issues.jboss.org/browse/JBIDE-22510 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Final > > > This is reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=495338 > In the mean time, we should disable the {{DockerHubRegistryTest}} tests to avoid the build failures on Jenkins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3922) Internal error occurs during installation when symbol "?" is used in installation path

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3922?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3922: ------------------------------ Component/s: installer > Internal error occurs during installation when symbol "?" is used in installation path > -------------------------------------------------------------------------------------- > > Key: JBDS-3922 > URL: https://issues.jboss.org/browse/JBDS-3922 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Environment: Fedora 23, x64 > Reporter: Ondrej Dockal > > When choosing an installation path during devstudio installation and the character of "?" is used, installation process ends up with an internal error message. I would expect that error message would more descriptive or adding such character into installation path while choosing the path would cause some kind of warning/error before installation process starts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

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 June 2016