April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19190) migrate VersionWatch to jbosstools-* repo

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-19190: -------------------------------------- [~max]. No problem to change a repo structure. However Max, right now VWatch contains additional JBDS installation scripts. Is it ok to keep them in jbosstools repo? If not then jenkins jobs will have to clone two repositories, one for VWatch and one for JBDS scripts? > migrate VersionWatch to jbosstools-* repo > ----------------------------------------- > > Key: JBIDE-19190 > URL: https://issues.jboss.org/browse/JBIDE-19190 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > 0. decide where to put this... under jbosstools-ci or some new repo? Create a new component in JIRA accordingly. > 1. remove all refs to QA Jenkins file paths to make this more generic > 2. migrate those internal file paths into jenkins config.xml files > 3. document how to do installs for Eclipse, JBT or JBDS BYOE via commandline for setting up the footprint of installs against which to do baseline version watches -- pre-existing doc here: > http://download.jboss.org/jbosstools/updates/scripted-installation/ > https://devstudio.redhat.com/download/scripted-install/ > 4. test #3 to ensure it works, and that a mix of "studio" and "eclipse" folders can be used in a vwatch report -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19064) Improve up/down version report in VWatch

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19064?page=com.atlassian.jira.plugi... ] Jiri Peterka resolved JBIDE-19064. ---------------------------------- Resolution: Done Up/Down indication added, see the screenshot. > Improve up/down version report in VWatch > ---------------------------------------- > > Key: JBIDE-19064 > URL: https://issues.jboss.org/browse/JBIDE-19064 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.2.Final > Reporter: Jiri Peterka > Assignee: Jiri Peterka > Fix For: 4.3.0.Alpha2 > > Attachments: up-down-indication.png > > > Improve reporting in Report / Product files so that the nature of the version up/down -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19064) Improve up/down version report in VWatch

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19064?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-19064: --------------------------------- Attachment: up-down-indication.png > Improve up/down version report in VWatch > ---------------------------------------- > > Key: JBIDE-19064 > URL: https://issues.jboss.org/browse/JBIDE-19064 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.2.Final > Reporter: Jiri Peterka > Assignee: Jiri Peterka > Fix For: 4.3.0.Alpha2 > > Attachments: up-down-indication.png > > > Improve reporting in Report / Product files so that the nature of the version up/down -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19350) big war deployment to remote server (management) gets stuck

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19350?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19350: --------------------------------------------- if there is a bug in the libraries we are using (wildfly client jars) our responsibility is at least to report them so they can become aware and potentially fix it. > big war deployment to remote server (management) gets stuck > ----------------------------------------------------------- > > Key: JBIDE-19350 > URL: https://issues.jboss.org/browse/JBIDE-19350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > Attachments: remote-publishing-stuck.png > > > I tried deploying an ear with a nested utility project to a remote EAP 6.3 server with the management profile and it got stuck during publishing (10 %). > I used the project from JBIDE-19043 - see "Steps to Reproduce". > !remote-publishing-stuck.png! > I wanted to get a more general use case before reporting this, but I'm still stuck at canceling of the publish task, so I decided to write this JIRA before killing off Eclipse - that is btw a serious problem as well - that you can't cancel the task. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17814) Empty editor is opened instead of Central editor

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17814?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-17814: ------------------------------------ I tried it again with JBDS 9 nightly (Alpha2-v20150414-2227-B2953) and issue is still present. I'm not sure it it's worth it to spend any more time on this as Central will be refactored in Beta1. > Empty editor is opened instead of Central editor > ------------------------------------------------ > > Key: JBIDE-17814 > URL: https://issues.jboss.org/browse/JBIDE-17814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta3 > Environment: Fedora 20 > Reporter: Radim Hopp > Assignee: Radim Hopp > Fix For: 4.2.x, 4.3.0.Alpha2 > > Attachments: central2.ogv > > > I seems to appear only with repetitive closing/opening Central editor. > Screencast: http://youtu.be/Z_X_Eo76wV8 > I can reproduce this issue even with GTK2. > There is no error in error log nor in console output. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17814) Empty editor is opened instead of Central editor

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17814?page=com.atlassian.jira.plugi... ] Radim Hopp reassigned JBIDE-17814: ---------------------------------- Assignee: Fred Bricon (was: Radim Hopp) > Empty editor is opened instead of Central editor > ------------------------------------------------ > > Key: JBIDE-17814 > URL: https://issues.jboss.org/browse/JBIDE-17814 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta3 > Environment: Fedora 20 > Reporter: Radim Hopp > Assignee: Fred Bricon > Fix For: 4.2.x, 4.3.0.Alpha2 > > Attachments: central2.ogv > > > I seems to appear only with repetitive closing/opening Central editor. > Screencast: http://youtu.be/Z_X_Eo76wV8 > I can reproduce this issue even with GTK2. > There is no error in error log nor in console output. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19496) docker run wizard

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19496?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19496: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > docker run wizard > ----------------- > > Key: JBIDE-19496 > URL: https://issues.jboss.org/browse/JBIDE-19496 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > Attachments: initial_idea_for_docker_run.bmml, initial_idea_for_docker_run.png > > > should have a docker wizard to easily run images. > The wizard should try and capture the most common things in smallest step necessary but still be flexible enough to be used for more advanced usecases. > For example, docker run --help returns ~50 options. We do not want to expose *All* as full ui elements but should try find a way to keep it simple. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19564?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19564: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Use background job to detect default connection settings > -------------------------------------------------------- > > Key: JBIDE-19564 > URL: https://issues.jboss.org/browse/JBIDE-19564 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19562) Allow for search and pull images from any Docker registry

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19562?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19562: ---------------------------------- Fix Version/s: 4.3.0.Beta1 > Allow for search and pull images from any Docker registry > --------------------------------------------------------- > > Key: JBIDE-19562 > URL: https://issues.jboss.org/browse/JBIDE-19562 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > The docker-client now allows for search on a docker registry, so we should leverage that API to search for images, display available info and let the user select the image(s) to pull on the current Docker deamon (ie, Docker host). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19563) Save docker connections in plugin preferences

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19563?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19563: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.0.Alpha2) > Save docker connections in plugin preferences > --------------------------------------------- > > Key: JBIDE-19563 > URL: https://issues.jboss.org/browse/JBIDE-19563 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Beta1 > > > In the current code, the Docker connections are not saved when exiting the workspace, so they need to be setup again after restart -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 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 April 2015