October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23291) If start of container fails on timeout, the status in server view is "Started, Synchronized"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23291?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23291: ------------------------------------- We mark the server as started once vagrant says the cdk is started and the vagrant up command has completed. If openshift is not running, we display a dialog to the user. This is because if we mark the server as stopped, the 'stop' action on the server adapter won't be enabled. The user will then try to start it again, and vagrant will reply that it is already up. The question is, why is it timing out at all? > If start of container fails on timeout, the status in server view is "Started, Synchronized" > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23291 > URL: https://issues.jboss.org/browse/JBIDE-23291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23347) Server New and Noteworthy for 4.4.2.AM2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23347?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-23347. ------------------------------- Resolution: Done All 12 issues were maintenance / small bug fixes. Nothing n&n > Server New and Noteworthy for 4.4.2.AM2 > --------------------------------------------------- > > Key: JBIDE-23347 > URL: https://issues.jboss.org/browse/JBIDE-23347 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Server4.4.2.AM2 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4084) Provide documentation using the installed studio

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-4084?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-4084: --------------------------------- Hi folks, I got a notification about this issue not having a fix version. [~aurelien.pupier], have you had a look at the links above and do you have any other concerns/questions/feedback? > Provide documentation using the installed studio > ------------------------------------------------ > > Key: JBDS-4084 > URL: https://issues.jboss.org/browse/JBDS-4084 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: documentation, platform-installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > > when following the getting started http://developers.redhat.com/products/devsuite/get-started/ > at the ned it redirect to the "command-line" version to use Containers. > it would be really better to provide tutorials to use the installed JBDS and the pre-configured CDK which is available in Servers view. > Personal note: I wasn't able to find by myself how do it in the Studio, I'm representing a UI-lover end-user, I asked for help on Devsuite HipChat channel -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Misha Ali reassigned JBDS-3903: ------------------------------- Assignee: Misha Ali (was: Xavier Coulon) > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Misha Ali > Fix For: 10.2.0.AM3 > > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23379) set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23379?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23379: ------------------------------- Story Points: 4 Sprint: devex #122 October 2016 > set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23379 > URL: https://issues.jboss.org/browse/JBIDE-23379 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > We should have a jenkins that builds [openshift-restclient-java|https://github.com/openshift/openshift-restclie...], deploys it to repository.jboss.org and triggers a rebuild of the [openshift client plugin|https://github.com/jbosstools/jbosstools-openshift/tree/master/plu...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4077: ----------------------------- Sprint: devex #122 October 2016 > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Marián Labuda > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23379) set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23379?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23379: ------------------------------- Summary: set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus (was: Client: setup jenkins build) > set up CI jobs for https://github.com/openshift/openshift-restclient-java, which deploy to nexus > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23379 > URL: https://issues.jboss.org/browse/JBIDE-23379 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > We should have a jenkins that builds [openshift-restclient-java|https://github.com/openshift/openshift-restclie...], deploys it to repository.jboss.org and triggers a rebuild of the [openshift client plugin|https://github.com/jbosstools/jbosstools-openshift/tree/master/plu...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Nick Boldt closed JBIDE-3509. ----------------------------- Fix Version/s: 4.4.2.AM2 (was: LATER) Assignee: Nick Boldt Resolution: Out of Date > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Optional > Fix For: 4.4.2.AM2 > > Attachments: eclipse-jbosstools-openshift-in-dropins.png, eclipse-jbosstools-server.png > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23370 at 10/17/16 9:09 PM: -------------------------------------------------------------- Rules for a .Final TP: a) can't be a snapshot URL as input b) can't be a snapshot VERSION as input I don't plan to finalize the TP until we're much closer to GA. But maybe you want to update the TP used for 4.4.2/10.2.0 AM3 to a newer version of Red Deer, then again when we freeze for GA, three weeks later? Deadlines for submission: Nov 02: AM3 target platform freeze Nov 23: GA target platform freeze was (Author: nickboldt): Rules for a .Final TP: a) can't be a snapshot URL as input b) can't be a snapshot VERSION as input I don't plan to finalize the TP until we're much closer to GA. But maybe you want to update the TP in AM3 to a newer version of Red Deer, then again when we freeze for GA, three weeks later? Deadlines for submission: Nov 02: AM3 target platform freeze Nov 23: GA target platform freeze > Update RedDeer in TP for JBT 4.4.2.AM3 > -------------------------------------- > > Key: JBIDE-23370 > URL: https://issues.jboss.org/browse/JBIDE-23370 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. > This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released. > We will want to update RedDeer in the TP to include the latest from > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP. > So please let me know when you're ready for this task and then I can create the update site immediately. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23370) Update RedDeer in TP for JBT 4.4.2.AM3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23370?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23370: ------------------------------------ Rules for a .Final TP: a) can't be a snapshot URL as input b) can't be a snapshot VERSION as input I don't plan to finalize the TP until we're much closer to GA. But maybe you want to update the TP in AM3 to a newer version of Red Deer, then again when we freeze for GA, three weeks later? Deadlines for submission: Nov 02: AM3 target platform freeze Nov 23: GA target platform freeze > Update RedDeer in TP for JBT 4.4.2.AM3 > -------------------------------------- > > Key: JBIDE-23370 > URL: https://issues.jboss.org/browse/JBIDE-23370 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.2.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP. > This was requested by [~rawagner] and we understand that it's just past code freeze for AM2, so this will probably have to wait until after AM2 is released. > We will want to update RedDeer in the TP to include the latest from > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > I will simply create a snapshot with the rsync script and then give you the url. But it's a bit premature to do it now since it may be a week or two before you actually update the TP. > So please let me know when you're ready for this task and then I can create the update site immediately. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016