February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-73) JSON Editor missing some icon(s?) [EBZ#487036]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-73: -------------------------------------- Summary: JSON Editor missing some icon(s?) [EBZ#487036] Key: ERT-73 URL: https://issues.jboss.org/browse/ERT-73 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot After installing the JSON editor from http://download.eclipse.org/webtools/downloads/drops/R3.8.0/S-3.8.0M5-201... it appears at least 1 icon is missing from the build. It's pretty visible in http://screencast.com/t/SVig7rgdDY -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-74) JSON Editor feature missing is uncategorized in the update site [EBZ#487038]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-74: -------------------------------------- Summary: JSON Editor feature missing is uncategorized in the update site [EBZ#487038] Key: ERT-74 URL: https://issues.jboss.org/browse/ERT-74 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot The JSON Editor feature can not be found under http://download.eclipse.org/webtools/downloads/drops/R3.8.0/S-3.8.0M5-201..., unless "Group items by category" is unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21363) create bugzilla importer for JIRA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21363?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21363: ------------------------------------ Now running in Jenkins: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-b... > create bugzilla importer for JIRA > --------------------------------- > > Key: JBIDE-21363 > URL: https://issues.jboss.org/browse/JBIDE-21363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.4.0.Alpha1 > > > Looking to create some kind of jiralint-like scraper tool to facilitate JIRA-like scrum/dashboard tracking of upstream projects, not located in JBoss JIRA. > This scraper would: > * [REQ1] find all bugzillas associated with a particular query, such as https://bugs.eclipse.org/bugs/buglist.cgi?status_whiteboard=RHT (18 issues) > * [REQ2] generate a JIRA for each one found (no dupes should be created) > * [REQ3] scrape several fields: product, component, version, target milestone, comment #0, summary, bug # > * [REQ4] need a mapping table for Eclipse-prod:proj:component:fixversion-or-target-milestone to Neon milestone so we can set default values for affectsversion/fixversion/targetrelease in created JIRAs. > * [REQ5] need a mapping table for Eclipse-prod:proj:component to ERT:component, eg., WTP:JSDT -> javascript > * [REQ6] created test issues here: https://issues.stage.jboss.org/browse/ERT > * [REQ7] run as a Jenkins job every 3 hours > Generated JIRA example: > {code} > title: (scraped from summary) Support for smart Import Mechanism [Eclipse BZ 464535] > issue link: (scraped from BZ ID#) https://bugs.eclipse.org/464535 > description: (scraped from BZ comment #0) > affectsversion: (scraped from BZ version 1.6.0) > fixversion: (scraped from BZ target milestone ---) > component: (scraped from product:component = m2e:ui) > labels: RHT, ERT > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21590) Explorer: OpenShift connection is not refreshed upon project deletion

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21590?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21590: --------------------------------------- Just merged https://issues.jboss.org/browse/JBIDE-21457. Does this resolve the issue described here? i just: 1. Expanded my openshift connection 2. Selected a project and deleted. 3. Confirmed deletion. 4. Project is no longer visible in explorer. 5. Confirmed project is not listed in project list for import app. > Explorer: OpenShift connection is not refreshed upon project deletion > --------------------------------------------------------------------- > > Key: JBIDE-21590 > URL: https://issues.jboss.org/browse/JBIDE-21590 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.1.CR1 > > > Upon deletion of a project under a connection in OpenShift explorer view, the deleted project is still visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-552 at 2/2/16 3:11 PM: ---------------------------------------------------------- So, to set this up, I need the list of URLs to use as the installation input, or INSTALL_PLAN: {code} # jbosstools_site_stream = master, 4.3.mars, 4.4.neon # SET = central, earlyaccess if [[ ${PROJECT} == "jbosstools" ]]; then INSTALL_PLAN="http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis..." elif [[ ${PROJECT} == "devstudio" ]]; then INSTALL_PLAN="https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c..." fi {code} Paul, can you provide URLs for the latest nightly/snapshot/CI builds of your input sites? We could either use the URLs you have in ide-config.properties, or to mirror what I'm doing above, you would use sites that include ONLY the IS content (not the IS content mixed in with JBT/JBDS via a composite site). We could do BOTH types of tests (install just the stack; install stack + JBT or JBDS), so if you want both types of install test, we'll need TWO sets of URLs and TWO jobs. was (Author: nickboldt): So, to set this up, I need the list of URLs to use as the installation input: {code} # jbosstools_site_stream = master, 4.3.mars, 4.4.neon # SET = central, earlyaccess if [[ ${PROJECT} == "jbosstools" ]]; then INSTALL_PLAN="http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis..." elif [[ ${PROJECT} == "devstudio" ]]; then INSTALL_PLAN="https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c..." fi {code} Paul, can you provide URLs for the latest nightly/snapshot/CI builds of your input sites? We could either use the URLs you have in ide-config.properties, or to mirror what I'm doing above, you would use sites that include ONLY the IS content (not the IS content mixed in with JBT/JBDS via a composite site). We could do BOTH types of tests (install just the stack; install stack + JBT or JBDS), so if you want both types of install test, we'll need TWO sets of URLs and TWO jobs. > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-552: ---------------------------------- So, to set this up, I need the list of URLs to use as the installation input: {code} # jbosstools_site_stream = master, 4.3.mars, 4.4.neon # SET = central, earlyaccess if [[ ${PROJECT} == "jbosstools" ]]; then INSTALL_PLAN="http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-dis..." elif [[ ${PROJECT} == "devstudio" ]]; then INSTALL_PLAN="https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.c..." fi {code} Paul, can you provide URLs for the latest nightly/snapshot/CI builds of your input sites? We could either use the URLs you have in ide-config.properties, or to mirror what I'm doing above, you would use sites that include ONLY the IS content (not the IS content mixed in with JBT/JBDS via a composite site). We could do BOTH types of tests (install just the stack; install stack + JBT or JBDS), so if you want both types of install test, we'll need TWO sets of URLs and TWO jobs. > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21631) Add unit tests for caching and DeploymentResourceMapper.java

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21631: ------------------------------------- Summary: Add unit tests for caching and DeploymentResourceMapper.java Key: JBIDE-21631 URL: https://issues.jboss.org/browse/JBIDE-21631 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Jeff Cantrill Fix For: 4.3.x Add unit tests to this complex class -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-552: -------------------------------- Summary: create install tests for JBTIS/JBDSIS Key: JBTIS-552 URL: https://issues.jboss.org/browse/JBTIS-552 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 4.3.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.3.0.Beta1 Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) Should be based on JBT/JBDS p2director install job [1]. [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-552) create install tests for JBTIS/JBDSIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-552: ----------------------------- Component/s: target-platform > create install tests for JBTIS/JBDSIS > ------------------------------------- > > Key: JBTIS-552 > URL: https://issues.jboss.org/browse/JBTIS-552 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Implement p2director install tests for JBTIS & JBDSIS to verify no missing deps in TP and no conflicting install deps (eg., different IS projects w/ conflicting singleton dependencies) > Should be based on JBT/JBDS p2director install job [1]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Later we could also create a job that maps to the JBT/JBDS install-grinder job [2]. > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21630) itest timeout not respected

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21630?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21630: ------------------------------- Labels: help_wanted (was: ) > itest timeout not respected > --------------------------- > > Key: JBIDE-21630 > URL: https://issues.jboss.org/browse/JBIDE-21630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: help_wanted > Fix For: 4.4.0.Alpha1 > > > Server itests are running with a timeout of 2400s, which is the default set in our parent pom [1]. > [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > But the server root pom sets a timeout of 3000s [2], which is being ignored [3]: > [2] https://github.com/jbosstools/jbosstools-server/blob/master/pom.xml#L17-L18 > {code} > 13:39:42 [ERROR] Timeout 2400 s exceeded. Process was killed. > {code} > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > So... how can we ensure that the itests get more time to run, so that these extra tests can be run without crashing? Currently, server is showing 2829 tests, but the last time it was blue, we had 3434 tests, so there are about 600 tests for which no results are being logged due to the timeout. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016