May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4414) Add DevSuite Installation to control panel

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4414?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4414: -------------------------------- Story Points: 5 Sprint: devex #132 May 2017 > Add DevSuite Installation to control panel > ------------------------------------------ > > Key: JBDS-4414 > URL: https://issues.jboss.org/browse/JBDS-4414 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 11.0.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4414) Add DevSuite Installation to control panel

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4414?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4414: ----------------------------------- Assignee: Denis Golovin > Add DevSuite Installation to control panel > ------------------------------------------ > > Key: JBDS-4414 > URL: https://issues.jboss.org/browse/JBDS-4414 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: New_and_noteworthy, Sprint_Demo > Fix For: 11.0.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4414) Add DevSuite Installation to control panel

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4414: ----------------------------------- Summary: Add DevSuite Installation to control panel Key: JBDS-4414 URL: https://issues.jboss.org/browse/JBDS-4414 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Reporter: Denis Golovin -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1082) SwitchYard specific updates to separate it from Fuse proper.

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1082?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick edited comment on JBTIS-1082 at 5/25/17 3:17 PM: ------------------------------------------------------------------- Hi [~naciao]! [~pleacu] mentioned on Mattermost that we need to remove the SwitchYard-specific doc/help files from the Fuse Tooling docs and migrate them into the SwitchYard world since we're pulling SY out of Fuse as it moves to Dev Studio. Can you or [~tcohen] or [~jmurphey] create a PR against the Fuse Tools docs and let us know what we do to make this transition? Thank you! was (Author: bfitzpat): Hi [~naciao]! [~pleacu] mentioned on Mattermost that we need to remove the SwitchYard-specific doc/help files from the Fuse Tooling docs and migrate them into the SwitchYard world since we're pulling SY out of Fuse as it moves to Dev Studio. Can you or [~tcohen] create a PR against the Fuse Tools docs and let us know what we do to make this transition? Thank you! > SwitchYard specific updates to separate it from Fuse proper. > ------------------------------------------------------------ > > Key: JBTIS-1082 > URL: https://issues.jboss.org/browse/JBTIS-1082 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > > Separate SwitchYard from Fuse Tooling proper. It should exist as a independent jar bundle. > Initial effort: - update to Oxygen JBTIS target platform > 1. Modify that org.switchyard.tools.bpmn2.feature requirement to be org.eclipse.bpmn2.modeler.feature.group [1.3.0,1.4.0] > 2. Pick up 4.5.0.AM1-SNAPSHOT as your JBTIS TP -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1082) SwitchYard specific updates to separate it from Fuse proper.

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1082?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBTIS-1082: ------------------------------------------ Hi [~naciao]! [~pleacu] mentioned on Mattermost that we need to remove the SwitchYard-specific doc/help files from the Fuse Tooling docs and migrate them into the SwitchYard world since we're pulling SY out of Fuse as it moves to Dev Studio. Can you or [~tcohen] create a PR against the Fuse Tools docs and let us know what we do to make this transition? Thank you! > SwitchYard specific updates to separate it from Fuse proper. > ------------------------------------------------------------ > > Key: JBTIS-1082 > URL: https://issues.jboss.org/browse/JBTIS-1082 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > > Separate SwitchYard from Fuse Tooling proper. It should exist as a independent jar bundle. > Initial effort: - update to Oxygen JBTIS target platform > 1. Modify that org.switchyard.tools.bpmn2.feature requirement to be org.eclipse.bpmn2.modeler.feature.group [1.3.0,1.4.0] > 2. Pick up 4.5.0.AM1-SNAPSHOT as your JBTIS TP -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-509) Add way to specify seccomp when running a container [EBZ#517223]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-509?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-509. ------------------------------- Fix Version/s: Oxygen (4.7) Resolution: Done > Add way to specify seccomp when running a container [EBZ#517223] > ---------------------------------------------------------------- > > Key: ERT-509 > URL: https://issues.jboss.org/browse/ERT-509 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > Fix For: Oxygen (4.7) > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-509) Add way to specify seccomp when running a container [EBZ#517223]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-509?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-509: --------------------------------- Assignee: Jeff Johnston > Add way to specify seccomp when running a container [EBZ#517223] > ---------------------------------------------------------------- > > Key: ERT-509 > URL: https://issues.jboss.org/browse/ERT-509 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-509) Add way to specify seccomp when running a container [EBZ#517223]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-509?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-509: ------------------------------ Sprint: devex #132 May 2017 > Add way to specify seccomp when running a container [EBZ#517223] > ---------------------------------------------------------------- > > Key: ERT-509 > URL: https://issues.jboss.org/browse/ERT-509 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24509) No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24509?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-24509: -------------------------------------- There is known issue - conflict between versions of some plugins. You have probably met the "Remedition Page" during the installation. If so, please choose "Update my installation..." on this page and continue with the installation. Please notice that a choice "Keep my installation the same..." which is selected by default are saying that OpenShift 3 wont be installed. !OpenShift3.png|thumbnail! > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final > ------------------------------------------------------------------------ > > Key: JBIDE-24509 > URL: https://issues.jboss.org/browse/JBIDE-24509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Environment: JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Eclipse Neon 4.6.1 > Fedora 24 and Windows 10 > Reporter: Xia Zhao > Priority: Blocker > Attachments: OpenShift3.png, Screenshot from 2017-05-25 13-37-32.png, Screenshot from 2017-05-25 14-25-53.png > > > Description of problem: > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final, after installation, only these 3 tools exist without having the openshift v3 tools: > JBoss OpenShift 2 Tools > JBoss OpenShift JavaScript Tools > JBoss Tools EGit Integration > Version-Release number of selected component (if applicable): > JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > How reproducible: > Always > Steps to Reproduce: > 1.Install JBT for Openshift v3 Tools according to http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...: > --> Add the following URL to Eclipse Neon 4.6.1 installation via: > Help > Install New Software... > Work with: > http://download.jboss.org/jbosstools/neon/stable/updates/ > Then select all the components, choose to install them. > 2. Restart Eclipse Neon 4.6.1 after JTB installation finished > 3. Go into Openshift Explorer window, click on "New Connections Wizard", choose "Openshift 3" for server type, the Authentication panel is empty > 4. Go to Help > Intallation Details, search for openshift > Actual results: > 4. JBoss OpenShift 3 Tools are not installed, only the following 3 exist: > JBoss OpenShift 2 Tools 3.3.3.v20170510-1453 org.jboss.tools.openshift.express.feature.feature.group JBoss by Red Hat > JBoss OpenShift JavaScript Tools 3.3.3.v20170502-0607 org.jboss.tools.openshift.js.feature.feature.group JBoss by Red Hat > JBoss Tools EGit Integration 3.3.3.v20170405-1252 org.jboss.tools.openshift.egit.integration.feature.feature.group JBoss by Red Hat > Expected results: > JBoss OpenShift 3 Tools should be installed if following http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Additional info: > Issue reproduced on both Fedora 24 and Windows 10. > This is a regression, with old JBT build 4.3.3 Final, the openshift 3 tools existed and worked fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24509) No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24509?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-24509: --------------------------------- Attachment: OpenShift3.png > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final > ------------------------------------------------------------------------ > > Key: JBIDE-24509 > URL: https://issues.jboss.org/browse/JBIDE-24509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Environment: JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Eclipse Neon 4.6.1 > Fedora 24 and Windows 10 > Reporter: Xia Zhao > Priority: Blocker > Attachments: OpenShift3.png, Screenshot from 2017-05-25 13-37-32.png, Screenshot from 2017-05-25 14-25-53.png > > > Description of problem: > No wizard for OpenShift 3 connections present in JBoss Tools 4.4.4.Final, after installation, only these 3 tools exist without having the openshift v3 tools: > JBoss OpenShift 2 Tools > JBoss OpenShift JavaScript Tools > JBoss Tools EGit Integration > Version-Release number of selected component (if applicable): > JBoss Tools 4.4.4.Final > http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > How reproducible: > Always > Steps to Reproduce: > 1.Install JBT for Openshift v3 Tools according to http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_...: > --> Add the following URL to Eclipse Neon 4.6.1 installation via: > Help > Install New Software... > Work with: > http://download.jboss.org/jbosstools/neon/stable/updates/ > Then select all the components, choose to install them. > 2. Restart Eclipse Neon 4.6.1 after JTB installation finished > 3. Go into Openshift Explorer window, click on "New Connections Wizard", choose "Openshift 3" for server type, the Authentication panel is empty > 4. Go to Help > Intallation Details, search for openshift > Actual results: > 4. JBoss OpenShift 3 Tools are not installed, only the following 3 exist: > JBoss OpenShift 2 Tools 3.3.3.v20170510-1453 org.jboss.tools.openshift.express.feature.feature.group JBoss by Red Hat > JBoss OpenShift JavaScript Tools 3.3.3.v20170502-0607 org.jboss.tools.openshift.js.feature.feature.group JBoss by Red Hat > JBoss Tools EGit Integration 3.3.3.v20170405-1252 org.jboss.tools.openshift.egit.integration.feature.feature.group JBoss by Red Hat > Expected results: > JBoss OpenShift 3 Tools should be installed if following http://tools.jboss.org/downloads/jbosstools/neon/4.4.4.Final.html#update_... > Additional info: > Issue reproduced on both Fedora 24 and Windows 10. > This is a regression, with old JBT build 4.3.3 Final, the openshift 3 tools existed and worked fine. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017