June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17882) Validate remote server dir before start/stop/deploy operations

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17882?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-17882. --------------------------------- I verified this with EAP 7 and devstudio 10. Although my verification is not 100%. When I save an empty path, it showed me an error when I tried to start the server. Likewise when I changed the path to a non-existent one. Then I wanted to try to start the server and then rename the deployments dir on the remote server, but that resulted in exceptions in the server log, so I didn't even try to deploy anything there. > Validate remote server dir before start/stop/deploy operations > -------------------------------------------------------------- > > Key: JBIDE-17882 > URL: https://issues.jboss.org/browse/JBIDE-17882 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Max said this on irc today: > {quote} > strykerawb: i got some really weird behavior 12:56:27 > maxandersen strykerawb: see this video: http://screencast.com/t/uSDT1EoS 12:56:31 > jbossbot Title: 014-07-15_1255 - max.rydahl.andersen's library 12:56:31 > maxandersen what is it doing? 12:56:34 > maxandersen this is me dragging a project to wildfly server 12:56:42 > maxandersen ah the server is configured as remote with blank remote server home... 12:57:05 > maxandersen seems that result in complete funky endless loop.. > {quote} > The problem is that he had an empty dir set up on a remote server. So when he tried to publish, this resulted in some unexpected behavior (endless copy progress in this case). > Currently, when you create a remote server, the dialog will not let you leave the server home dir empty. But that is not enough. You can still change it in the server editor to be empty. Rob says he wants to remove this field from the server editor and only use the wizard, but that is still not enough - the user can remote the folder on the remote system at a later time. > We probably don't need to check the folder every time we use it, but at least at the start of each operation such as start/stop server, publish to server. > Also, the New server dialog checks for empty string, but I'm not 100 % sure if it actually checks that the folder exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22670) tools.jboss.org/downloads refers to devstudio 9.1.0 even after 10.0 GA release

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22670?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22670. --------------------------------- Verified. > tools.jboss.org/downloads refers to devstudio 9.1.0 even after 10.0 GA release > ------------------------------------------------------------------------------ > > Key: JBIDE-22670 > URL: https://issues.jboss.org/browse/JBIDE-22670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Final > > > 10.0.0.GA (Neon) is available - http://tools.jboss.org/downloads/devstudio/neon/10.0.0.GA.html > but http://tools.jboss.org/downloads/ still refers to 9.1.0.GA (Mars) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22575) Extract CDK's Docker registry from vagrant service-manager env

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22575?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22575. --------------------------------- So I finally verified this in devstudio 10.0.0.GA. We did see it work before, but to make sure that the url is really taken from service-manager a bit more was needed. So with the help of Marian and Radim, I changed the route in the vagrant box to return wtf.openshift.rhel-cdk.10.1.2.2.xip.io . Then I started the server adapter in devstudio and it correctly showed this url in the newly created openshift connection. Then I also wanted to make sure that this will work in case service-manager doesn't return anything. So I installed an old service-manager version 0.0.3 which doesn't show the registry url. And even with that, the created connection included the default url: https://hub.openshift.rhel-cdk.10.1.2.2.xip.io There is one small catch though - the hardcoded string has a trailing space. That looks like a bug - logged here: JBIDE-22671 . > Extract CDK's Docker registry from vagrant service-manager env > -------------------------------------------------------------- > > Key: JBIDE-22575 > URL: https://issues.jboss.org/browse/JBIDE-22575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.4.0.Final > > > The docker registry url is currently hard coded when created a new OpenShift connection for the CDK (JBIDE-22441). > With https://github.com/projectatomic/vagrant-service-manager/issues/210 being fixed and the CDK 2.1 looming around the corner, it's now possible to get the DOCKER_REGISTRY value from the CDK: > {code} > vagrant service-manager env > # docker env: > # Set the following environment variables to enable access to the > # docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.1.2.2:2376 > export DOCKER_CERT_PATH=/Users/fbricon/Dev/openshift/cdk.old/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.21 > # openshift env: > # You can access the OpenShift console on: https://10.1.2.2:8443/console > # To use OpenShift CLI, run: oc login https://10.1.2.2:8443 > export OPENSHIFT_URL=https://10.1.2.2:8443 > export OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console > export DOCKER_REGISTRY=hub.openshift.rhel-cdk.10.1.2.2.xip.io > {code} > We should store the docker registry with a https:// prefix, if the value is not a URL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22671) Hardcoded docker registry url contains a trailing space

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22671?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22671: --------------------------------------- I tried to push an image to the registry and it seems the trailing space is not a problem. But I guess it's still nicer to lose the space. > Hardcoded docker registry url contains a trailing space > ------------------------------------------------------- > > Key: JBIDE-22671 > URL: https://issues.jboss.org/browse/JBIDE-22671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > JBIDE-22441 added a hardcoded url for docker registry url for cdk/openshift. > But there is a trailing space in the url: > https://github.com/jbosstools/jbosstools-openshift/commit/132cea25129ffca... > That looks like an error? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22671) Hardcoded docker registry url contains a trailing space

by Martin Malina (JIRA)

Martin Malina created JBIDE-22671: ------------------------------------- Summary: Hardcoded docker registry url contains a trailing space Key: JBIDE-22671 URL: https://issues.jboss.org/browse/JBIDE-22671 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.4.0.Final Reporter: Martin Malina Assignee: Rob Stryker JBIDE-22441 added a hardcoded url for docker registry url for cdk/openshift. But there is a trailing space in the url: https://github.com/jbosstools/jbosstools-openshift/commit/132cea25129ffca... That looks like an error? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22499) Read CDK's Docker Registry url from service manager plugin

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22499?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22499. --------------------------------- Closing duplicate. > Read CDK's Docker Registry url from service manager plugin > ---------------------------------------------------------- > > Key: JBIDE-22499 > URL: https://issues.jboss.org/browse/JBIDE-22499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final, 4.4.1.M1 > > > we need to get the docker registry url from adb-utils (https://github.com/projectatomic/adb-utils/issues/113) and store it in the connection properties (See API in JBIDE-22314) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3914) Build zip distribution for Mac OS X and Linux

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3914?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3914: ----------------------------------- Assignee: Denis Golovin (was: Nick Boldt) > Build zip distribution for Mac OS X and Linux > --------------------------------------------- > > Key: JBDS-3914 > URL: https://issues.jboss.org/browse/JBDS-3914 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.0.1.M1 > > Attachments: zip in exe fails.png > > > We need to check if self extracting 7zip understands zip format and instead of creating .7z archive use zip archve for bundled installer. that would let us release the same zip as Linux and Mac OS X distribution. The only change is creating readme.md in the archive root with link to installation guide (see trelo card for details). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3829) Installer does not start properly when the user has control characters in the name

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3829?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3829: -------------------------------- Sprint: (was: devex #116 June 2016) > Installer does not start properly when the user has control characters in the name > ---------------------------------------------------------------------------------- > > Key: JBDS-3829 > URL: https://issues.jboss.org/browse/JBDS-3829 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.1.M1 > > > Surprisingly, windows allows usernames such as n&o#t.e-r!u(e)r > With such a name, the installer does not even load the first page. It looks like it can't load some file, but I didn't get any error message out of it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Sprint: (was: devex #116 June 2016) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.1.M1 > > Attachments: Installer-not-signed-tc.PNG > > > When you login with an active account that hasn't signed the Terms and Conditions the login fails and tells you why but not how to resolve it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22619: ------------------------------------ Note that using M* means that a user who has a M* version installed will have to uninstall to update to GA or Final, because OSGI rules say M > G > F. We could consider two alternative approaches: a) use AM, DM, EM for "A milestone", "development milestone" or "engineering milestone" instead of just M b) use lowercase qualifiers "final" and "ga", because in OSGi rules (ASCII table), uppercase is less than lowercase, so M < f < g > Decide strategy for fixversion targets in JIRA > ---------------------------------------------- > > Key: JBIDE-22619 > URL: https://issues.jboss.org/browse/JBIDE-22619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.4.1.M1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.1.M1 > > > We need to decide the strategy for milestones / fixversions in JIRA. > One suggestion has been to align fixversions w/ sprint numbers, thus: > * 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...? > instead of > * 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ? > Questions/concerns: > * what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders (4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which sprint applies? > * whatever schema we adopt has to work with bzira and jiralint > * any other systems that parse JIRA for integration purposes? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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