February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21643) use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ?

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21643?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21643: ---------------------------------------- Yes. > use rebuilt Birt 1.8.0 or build 1.8.1 (with no changes) ? > --------------------------------------------------------- > > Key: JBIDE-21643 > URL: https://issues.jboss.org/browse/JBIDE-21643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: birt, build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.3.1.CR1 > > > Since feature freeze is done for Birt 1.8.x in JBT 4.3.1.Beta2, we have two choices for what to include in JBT 4.3.1.CR1 and .Final: > a) since nothing important has happened in the 4.3.x branch [1] of jbosstools-birt, we could re-use the 1.8.0.Final bits, which I've just rebuilt [2] from the 4.3.0.Final tag, and published [3]. > b) or we could upversion the 1.8.1.Beta2 bits to 1.8.1.CR1 (and then later to 1.8.1.Final) even though there's functionally nothing new in there beyond what was released in 1.8.0.Final on Sept 24. > [1] https://github.com/jbosstools/jbosstools-birt/commits/jbosstools-4.3.x > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-birt_4.3.m... > [3] http://download.jboss.org/jbosstools/mars/stable/updates/core/birt/1.8.0.... > I'm inclined to go with the rebuilt 1.8.0 instead of the needlessly upversioned 1.8.1. > WDYT? -- 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 Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-552?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-552: ---------------------------------- [~nickboldt] - that sounds perfect! > 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-20719) Updating a token for OpenShift 3 connection via Edit Connection does not update resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20719?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20719: ----------------------------------- Assignee: Viacheslav Kabanovich > Updating a token for OpenShift 3 connection via Edit Connection does not update resources > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20719 > URL: https://issues.jboss.org/browse/JBIDE-20719 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1 > > > If token storage in secure storage expires and new one is required to be able to work with OpenShift 3 connection, then updating token via Edit Connection dialog does not automatically update connection. There is still error tree item under resources saying to obtain a new token. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21650) Make Import OS3 Application more context-oriented

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21650?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21650. --------------------------------- Fix Version/s: 4.3.1.CR1 Assignee: Fred Bricon Resolution: Done Done as part of JBIDE-21617. See screencast http://screencast.com/t/6yiVDc1I9QfW > Make Import OS3 Application more context-oriented > ------------------------------------------------- > > Key: JBIDE-21650 > URL: https://issues.jboss.org/browse/JBIDE-21650 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: import_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > Currently we don't make difference from where Import Application... context menu item in OpenShift Explorer view is invoked. If a connection contains 2 and more projects, and at least 2 of those projects contains a build config, there are always listed all projects with build configs in Import OpenShift Application wizard no matter what. Even if I have selected a specific service or project, invoked Import Application wizard lists all projects and build configs. It would be nice to have it more context oriented - when select Import Application... context menu item on a specific service, build config related to this service should be preselected in wizard (maybe only project where the service is located should be listed and its build configs with selected the selected one). If opened via context menu of a project, project should be preselected (maybe only project with its build config could be visible). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21645) No build config warning dialog shown when opening Import Application... on OS3 connection

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21645?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21645. --------------------------------- Fix Version/s: 4.3.1.CR1 Resolution: Done ok so Import Application menu is now removed from OS3 Connections' context. > No build config warning dialog shown when opening Import Application... on OS3 connection > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21645 > URL: https://issues.jboss.org/browse/JBIDE-21645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: import_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: no_build_config.png > > > When I am trying to import a new application via connection context menu Import Application..., I get following warning dialog > !no_build_config.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21653) Implement Red Deer classes to support testing of Arquillian preferences UI pages

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21653?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-21653: -------------------------------------- https://github.com/jbosstools/jbosstools-integration-tests/pull/1439 > Implement Red Deer classes to support testing of Arquillian preferences UI pages > -------------------------------------------------------------------------------- > > Key: JBIDE-21653 > URL: https://issues.jboss.org/browse/JBIDE-21653 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.1.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21653) Implement Red Deer classes to support testing of Arquillian preferences UI pages

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21653?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-21653: ------------------------------------ Assignee: Len DiMaggio > Implement Red Deer classes to support testing of Arquillian preferences UI pages > -------------------------------------------------------------------------------- > > Key: JBIDE-21653 > URL: https://issues.jboss.org/browse/JBIDE-21653 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.1.Beta2 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21653) Implement Red Deer classes to support testing of Arquillian preferences UI pages

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-21653: ------------------------------------ Summary: Implement Red Deer classes to support testing of Arquillian preferences UI pages Key: JBIDE-21653 URL: https://issues.jboss.org/browse/JBIDE-21653 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.3.1.Beta2 Reporter: Len DiMaggio -- 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: --------------------------------------- [~fbricon] Added project cache to handle project changes and control loading of project in 'getChildrenFor > 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 > > Attachments: video.ogg-1.ogv > > > 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-550) Update to latest Mars Graphiti 0.13

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-550?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-550 at 2/4/16 2:46 PM: ---------------------------------------------------------- Issue is a CRC error in graphiti - new graphiti due out Friday - Feb 5 https://issues.jboss.org/browse/JBDS-3586?focusedCommentId=13157181&page=... *Reason:* Update graphiti capture to avoid crc issue. Update to 4.3.1.Beta2 core. *Project page/sources:* *Version:* S-0.13.0M5-201602031129 *License and owner:* EPL *Original p2 repo:* http://download.eclipse.org/graphiti/updates/milestones/S-0.13.0M5-201602... *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/S-0.13... *Include Sources:* Yes *Affected JBoss Tools components:* JBDSIS *Include in JBDS:* Yes (JBDSIS) *Type of dependency:* distribution *List of bundles added/removed:* {code} Graphiti update: === Summary === [pleacu@pleacu-2-laptop x86_64]$ more ~/temp/diff-tpea < org.eclipse.graphiti.feature.feature.group [0.13.0.v20150818-1354] < org.eclipse.graphiti.mm [0.13.0.v20150818-1354] < org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20150818-1354] < org.eclipse.graphiti.ui [0.13.0.v20150818-1354] < org.eclipse.graphiti.ui.capabilities [0.13.0.v20150818-1354] < org.eclipse.graphiti [0.13.0.v20150818-1354] < org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20150818-1354] < org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20150818-1354] < org.eclipse.graphiti.doc [0.13.0.v20150818-1354] < org.eclipse.graphiti.pattern [0.13.0.v20150818-1354] < org.eclipse.graphiti.feature.feature.jar [0.13.0.v20150818-1354] < org.eclipse.graphiti.export.batik [0.13.0.v20150818-1354] > org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20160203-1129] > org.eclipse.graphiti.feature.feature.group [0.13.0.v20160203-1129] > org.eclipse.graphiti.mm [0.13.0.v20160203-1129] > org.eclipse.graphiti.feature.feature.jar [0.13.0.v20160203-1129] > org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20160203-1129] > org.eclipse.graphiti.pattern [0.13.0.v20160203-1129] > org.eclipse.graphiti.doc [0.13.0.v20160203-1129] > org.eclipse.graphiti.ui.capabilities [0.13.0.v20160203-1129] > org.eclipse.graphiti.export.batik [0.13.0.v20160203-1129] > org.eclipse.graphiti.ui [0.13.0.v20160203-1129] > org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20160203-1129] > org.eclipse.graphiti [0.13.0.v20160203-1129] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 12 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 12 unique IUs 4.3.1.Beta2 update: < org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.tests [3.6.1.Beta1-v20151212-0108-B64] < org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.central [2.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.project.examples [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.common.test [3.7.1.Beta1-v20151212-0108-B64] < org.jboss.tools.common.base.test [3.7.1.Beta1-v20151212-0108-B64] < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.jmx.core.test [1.7.1.Beta1-v20151212-0124-B73] < org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.project.examples [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.as.test.core [3.1.1.Beta1-v20151212-0124-B73] < org.jboss.tools.common [3.7.1.Beta1-v20151212-0108-B64] > org.jboss.tools.as.test.core [3.1.1.Beta2-v20160121-0132-B81] > org.jboss.tools.common.base.test [3.7.1.Beta2-v20160127-2129-B77] > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.common.test [3.7.1.Beta2-v20160127-2129-B77] > org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.tests [3.6.1.Beta2-v20160127-2129-B77] > org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.central [2.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.project.examples [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.common [3.7.1.Beta2-v20160127-2129-B77] > org.jboss.tools.jmx.core.test [1.7.1.Beta2-v20160121-0132-B81] > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.project.examples [3.0.1.Beta2-v20160121-2329-B74] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform.target.repo contains 16 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform.target.repo contains 16 unique IUs < org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.project.examples [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.project.examples [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta1-v20151215-1931-B68] < org.jboss.tools.community.central [2.0.1.Beta1-v20151215-1931-B68] > org.jboss.tools.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.central.feature.feature.group [2.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.central [2.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.project.examples.feature.feature.group [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.central.feature.feature.jar [2.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.community.project.examples [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.project.examples.feature.feature.jar [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.project.examples.cheatsheet [3.0.1.Beta2-v20160121-2329-B74] > org.jboss.tools.project.examples [3.0.1.Beta2-v20160121-2329-B74] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 10 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 10 unique IUs {code} was (Author: pleacu): Issue is a CRC error in graphiti - new graphiti due out Friday - Feb 5 https://issues.jboss.org/browse/JBDS-3586?focusedCommentId=13157181&page=... *Reason:* Update graphiti capture to avoid crc issue *Project page/sources:* *Version:* S-0.13.0M5-201602031129 *License and owner:* EPL *Original p2 repo:* http://download.eclipse.org/graphiti/updates/milestones/S-0.13.0M5-201602... *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/S-0.13... *Include Sources:* Yes *Affected JBoss Tools components:* JBDSIS *Include in JBDS:* Yes (JBDSIS) *Type of dependency:* distribution *List of bundles added/removed:* {code} === Summary === [pleacu@pleacu-2-laptop x86_64]$ more ~/temp/diff-tpea < org.eclipse.graphiti.feature.feature.group [0.13.0.v20150818-1354] < org.eclipse.graphiti.mm [0.13.0.v20150818-1354] < org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20150818-1354] < org.eclipse.graphiti.ui [0.13.0.v20150818-1354] < org.eclipse.graphiti.ui.capabilities [0.13.0.v20150818-1354] < org.eclipse.graphiti [0.13.0.v20150818-1354] < org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20150818-1354] < org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20150818-1354] < org.eclipse.graphiti.doc [0.13.0.v20150818-1354] < org.eclipse.graphiti.pattern [0.13.0.v20150818-1354] < org.eclipse.graphiti.feature.feature.jar [0.13.0.v20150818-1354] < org.eclipse.graphiti.export.batik [0.13.0.v20150818-1354] > org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20160203-1129] > org.eclipse.graphiti.feature.feature.group [0.13.0.v20160203-1129] > org.eclipse.graphiti.mm [0.13.0.v20160203-1129] > org.eclipse.graphiti.feature.feature.jar [0.13.0.v20160203-1129] > org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20160203-1129] > org.eclipse.graphiti.pattern [0.13.0.v20160203-1129] > org.eclipse.graphiti.doc [0.13.0.v20160203-1129] > org.eclipse.graphiti.ui.capabilities [0.13.0.v20160203-1129] > org.eclipse.graphiti.export.batik [0.13.0.v20160203-1129] > org.eclipse.graphiti.ui [0.13.0.v20160203-1129] > org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20160203-1129] > org.eclipse.graphiti [0.13.0.v20160203-1129] === Summary === file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 12 unique IUs file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 12 unique IUs {code} > Update to latest Mars Graphiti 0.13 > ----------------------------------- > > Key: JBTIS-550 > URL: https://issues.jboss.org/browse/JBTIS-550 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Mirror latest Graphiti to JBT. -- 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