May 2016 - jbosstools-issues - Jboss List Archives

[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 resolved JBIDE-22195. ----------------------------------- Resolution: Done > 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.0.Alpha2 > > > 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, 11 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: ---------------------------------- Description: 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 was: 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}}. > 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.0.Alpha2 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3890) Devstudio installation takes a long, long time

by Jan Richter (JIRA)

Jan Richter created JBDS-3890: --------------------------------- Summary: Devstudio installation takes a long, long time Key: JBDS-3890 URL: https://issues.jboss.org/browse/JBDS-3890 Project: Red Hat Developer Studio (DevStudio) Issue Type: Bug Components: installer Affects Versions: 10.0.0.Alpha1 Environment: Fedora 22 x64 OpenJDK 1.8.0_91 jboss-devstudio-10.0.0.Alpha1-v20160517-0518-B5370-installer-standalone.jar Reporter: Jan Richter Priority: Critical Attachments: install.png Some actual data here: - Alpha1 (staged) build took 2:05 to install on my machine - Alpha1 nightly (B5370) took 5:15 to install Around the minute mark the installation just freezes in this state: !install.png|thumbnail! Meanwhile the trace says: {noformat} Committing the provisioning operation. Operation completed in 275702 ms. {noformat} That is quite a long time it spent doing that operation. Some jstack info can be found here: http://pastebin.test.redhat.com/374700 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22355) Build qualifier still say Alpha2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22355: ---------------------------------------- {quote}one suggestion made is to even abandon the use of alpha/beta/etc. and just use sprint numbers, something like 4.4.0.s114{quote} If we still want all content we produce to have such a label changed from time to time and to have older builds still mentioning older sprint, then it won't change anything. the BUILD_ALIAS would just have different value, but the issue is having a BUILD_ALIAS that change with time from one version/sprint to another and that we want to propagate it.. To avoid constantly updating parent pom, it has now been identified multiple times that it implies getting rid of mentioning the milestone in artifacts we produce, and rely only a timestamps (build timestamp would be a 1st iteration, JBIDE-13671 could be considered in a 2nd iteration). If the only requirement is to have GA or Final labeled differently, then we can simply have a dedicated variable or profile to set when doing a GA. Something like BUILD_ALIAS=SNAPSHOT by default, and when doing a GA, we build with "-DBUILD_ALIAS=Final". > Build qualifier still say Alpha2 > -------------------------------- > > Key: JBIDE-22355 > URL: https://issues.jboss.org/browse/JBIDE-22355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1. > All those should be moved to Alpha2 (they should be moved just when branching/releasing actually) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3787: -------------------------------- Sprint: (was: devex #114 May 2016) > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha3 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22355) Build qualifier still say Alpha2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22355?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22355: --------------------------------------------- one suggestion made is to even abandon the use of alpha/beta/etc. and just use sprint numbers, something like 4.4.0.s114 but i'm not sure how we then actually keep track of when something is Final vs just intermediate builds. I'm all for finding a way to avoid constantly updating parent pom's, but we'll need devs to update their project pom's version instead afaics. Added [~akazakov] to watcher list. > Build qualifier still say Alpha2 > -------------------------------- > > Key: JBIDE-22355 > URL: https://issues.jboss.org/browse/JBIDE-22355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > Build qualifiers, parent pom version, and version of parent pom referenced by components are still Alpha1. > All those should be moved to Alpha2 (they should be moved just when branching/releasing actually) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3874) Rename default install folder to match the new branding

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3874?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3874: -------------------------------- Component/s: platform-installer (was: installer) > Rename default install folder to match the new branding > ------------------------------------------------------- > > Key: JBDS-3874 > URL: https://issues.jboss.org/browse/JBDS-3874 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.0.Alpha2 > > > Since we are no longer calling devstudio anything begining with 'j' (i.e. jboss devstudio, jbds, etc.) it would be nice to rename the default installation folder from 'jbdevstudio' to something more consistent with the new branding, like 'devstudio'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3874) Rename default install folder to match the new branding

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3874?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3874: ----------------------------------- Story Points: 1 Assignee: Denis Golovin > Rename default install folder to match the new branding > ------------------------------------------------------- > > Key: JBDS-3874 > URL: https://issues.jboss.org/browse/JBDS-3874 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.0.0.Alpha2 > > > Since we are no longer calling devstudio anything begining with 'j' (i.e. jboss devstudio, jbds, etc.) it would be nice to rename the default installation folder from 'jbdevstudio' to something more consistent with the new branding, like 'devstudio'. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3888) DevStudio build results should contain file with additional information

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3888?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3888: -------------------------------- Summary: DevStudio build results should contain file with additional information (was: DevStudio build results should contain file with additional biuild information) > DevStudio build results should contain file with additional information > ----------------------------------------------------------------------- > > Key: JBDS-3888 > URL: https://issues.jboss.org/browse/JBDS-3888 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: build, platform-installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > Assignee: Nick Boldt > > Current implementation hardcode DevStudio version/url into Platform-Installer. Would be good to be able to get this info form download location in form of content.json file: > {code}{ > "name": "Red Hat Developer Studio", > "description": "DevStudio 10.0.0.Alpha2 Nightly Build", > "fullVersion": "10.0.0.Alpha2-XXXXXXXXXXXXX-B0001", > "installer": "https//downloadhost.com/devstudio-10.0.0.Alpha2-XXXXXXXXXXX-B0001-installer.jar" > }{code} > Full URL is required to avoid download interruptions, when new version of DevStudio is uploaded and files available from stable URL is overwritten with latest nightly build. In this case a client downloaded content.json has direct link to installer jar from specific nightly location, which is usually kept for several days. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-746) JBDS 9.0 - OpenShift Online article missing from access.redhat.com

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-746?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-746: ------------------------------------ Done and added link here: https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/ [~supriya.bharadwaj] can you QE this one please? > JBDS 9.0 - OpenShift Online article missing from access.redhat.com > ------------------------------------------------------------------ > > Key: TOOLSDOC-746 > URL: https://issues.jboss.org/browse/TOOLSDOC-746 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Supriya Bharadwaj > Assignee: Misha Ali > Labels: OpenShift2 > > Convert article from asciidoc to MD and add to access.redhat.com for OS 2 > http://tools.jboss.org/documentation/howto/openshift_deployproj.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016