August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23013) Pull Docker Tooling bits into JBT builds more frequently

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23013?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23013: ------------------------------- Fix Version/s: 4.4.x > Pull Docker Tooling bits into JBT builds more frequently > -------------------------------------------------------- > > Key: JBIDE-23013 > URL: https://issues.jboss.org/browse/JBIDE-23013 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.x > > > It would be cool if we could update the Docker Tooling bits in our TP more frequently, i.e. weekly or even nightly. I know that currently it is quite a big effort to update TP. So we would need to simplify this somehow. > So this is a suggestion, but I don't know how we would do it or if it's doable at all. > Here's a bit of background: > Today I spotted this blocking bug in docker tooling: > https://issues.jboss.org/browse/JBIDE-23011 > It was probably brought into JBT TP in the last update of the TP - this JIRA: > https://issues.jboss.org/browse/JBIDE-22885 - 4 days ago. > Jeff Maury suggested, that it's a bad idea to update our TP this close to our release (AM3 in this case). But currently we don't have any other option. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Mat Booth edited comment on JBDS-3981 at 8/26/16 4:57 AM: ---------------------------------------------------------- Attaching the script I used to generate the above report -- it assumes that the rh-eclipse46-devstudio RPM is already installed. was (Author: mat.booth): Attaching the script I used to generate the above report > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Mat Booth updated JBDS-3981: ---------------------------- Attachment: feature_dupe_check.sh Attaching the script I used to generate the above report > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: feature_dupe_check.sh, IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ] Mat Booth commented on JBDS-3981: --------------------------------- Hey, I did a quick "sanity check" of the contents of the 301M package available at, http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.rpm... I found that you are packaging the following features that are already provided by other RPMs: org.eclipse.e4.rcp is provided by rh-eclipse46-eclipse-platform org.eclipse.equinox.p2.core.feature is provided by rh-eclipse46-eclipse-platform org.eclipse.equinox.p2.extras.feature is provided by rh-eclipse46-eclipse-platform org.eclipse.equinox.p2.rcp.feature is provided by rh-eclipse46-eclipse-platform org.eclipse.equinox.p2.user.ui is provided by rh-eclipse46-eclipse-platform org.eclipse.help is provided by rh-eclipse46-eclipse-platform org.eclipse.cvs is provided by rh-eclipse46-eclipse-pde org.eclipse.pde is provided by rh-eclipse46-eclipse-pde org.eclipse.draw2d is provided by rh-eclipse46-eclipse-gef org.eclipse.gef is provided by rh-eclipse46-eclipse-gef org.eclipse.linuxtools.docker.feature is provided by rh-eclipse46-eclipse-linuxtools-docker org.eclipse.tm.terminal.connector.local.feature is provided by rh-eclipse46-eclipse-tm-terminal-connectors org.eclipse.wst.web_ui.feature is provided by rh-eclipse46-eclipse-webtools-sourceediting > Build a new feature that omits features available from RPM install > ------------------------------------------------------------------ > > Key: JBDS-3981 > URL: https://issues.jboss.org/browse/JBDS-3981 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.1.0.GA > > Attachments: IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png > > > What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23047) 'Stop' action in CDK server context menu on Windows sometimes not available

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23047?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23047. --------------------------------- Fix Version/s: 4.2.1.Final Assignee: Rob Stryker Resolution: Done pushed a fix > 'Stop' action in CDK server context menu on Windows sometimes not available > --------------------------------------------------------------------------- > > Key: JBIDE-23047 > URL: https://issues.jboss.org/browse/JBIDE-23047 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.1.Final > > > The server cannot be stopped at all if the menu item isn't available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23047) 'Stop' action in CDK server context menu on Windows sometimes not available

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23047: ----------------------------------- Summary: 'Stop' action in CDK server context menu on Windows sometimes not available Key: JBIDE-23047 URL: https://issues.jboss.org/browse/JBIDE-23047 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.1.Final Reporter: Rob Stryker Priority: Critical The server cannot be stopped at all if the menu item isn't available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23046) If call to vagrant service-manager times out, openshift / docker connect should still try to be created

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23046?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23046. --------------------------------- Resolution: Done pushed to master > If call to vagrant service-manager times out, openshift / docker connect should still try to be created > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23046 > URL: https://issues.jboss.org/browse/JBIDE-23046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > In Windows, I was experiencing an error where the call to vagrant service-manager was not completing. This wasn't due to the output being unavailable, but rather the process not terminating. The current code throws a TimeoutException, but makes no attempt to check if the output is enough to still create the docker / openshift connections. > The code should attempt to survive the error and continue along. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23046) If call to vagrant service-manager times out, openshift / docker connect should still try to be created

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23046?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23046: -------------------------------- Story Points: 4 Sprint: devex #119 August 2016 > If call to vagrant service-manager times out, openshift / docker connect should still try to be created > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23046 > URL: https://issues.jboss.org/browse/JBIDE-23046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > In Windows, I was experiencing an error where the call to vagrant service-manager was not completing. This wasn't due to the output being unavailable, but rather the process not terminating. The current code throws a TimeoutException, but makes no attempt to check if the output is enough to still create the docker / openshift connections. > The code should attempt to survive the error and continue along. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23046) If call to vagrant service-manager times out, openshift / docker connect should still try to be created

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23046?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23046: ----------------------------------- Assignee: Rob Stryker > If call to vagrant service-manager times out, openshift / docker connect should still try to be created > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23046 > URL: https://issues.jboss.org/browse/JBIDE-23046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > In Windows, I was experiencing an error where the call to vagrant service-manager was not completing. This wasn't due to the output being unavailable, but rather the process not terminating. The current code throws a TimeoutException, but makes no attempt to check if the output is enough to still create the docker / openshift connections. > The code should attempt to survive the error and continue along. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23046) If call to vagrant service-manager times out, openshift / docker connect should still try to be created

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23046?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23046: -------------------------------- Fix Version/s: 4.4.1.Final > If call to vagrant service-manager times out, openshift / docker connect should still try to be created > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23046 > URL: https://issues.jboss.org/browse/JBIDE-23046 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.1.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Final > > > In Windows, I was experiencing an error where the call to vagrant service-manager was not completing. This wasn't due to the output being unavailable, but rather the process not terminating. The current code throws a TimeoutException, but makes no attempt to check if the output is enough to still create the docker / openshift connections. > The code should attempt to survive the error and continue along. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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