February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21711) Server Adapter: Need a way to restart modules

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21711?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21711: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Server Adapter: Need a way to restart modules > --------------------------------------------- > > Key: JBIDE-21711 > URL: https://issues.jboss.org/browse/JBIDE-21711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.CR1 > > > When doing hot code reload in an OpenShift deployed EAP server, changing a method signature will make the debugger complain with > !http://content.screencast.com/users/fbricon/folders/Jing/media/623c96cc-ae62-441b-b498-a39d9cf9b563/00000322.png|width=650! > Triggering a full publish on the module is not sufficient. > We need to at least have a way to trigger a module restart -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-295) utilize the tycho testing support for test bundles on JBTIS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-295?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-295: ---------------------------------- [~maxandersen] [~mickael_istria] - Opinions wanted... Looking at some older Jira - I believe all of the IS components now use the IS TP. Both JBTIS and JBDSIS are run through the p2 director install tests here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p... Also - SwitchYard uses the JBTIS TP and performs their own unit testing prior to being aggregated. Do you guys see a good use for using Mickael's p2installed surefire runtime test support at the IS level or does it not apply given unit testing at the component level? Thkx! > utilize the tycho testing support for test bundles on JBTIS > ----------------------------------------------------------- > > Key: JBTIS-295 > URL: https://issues.jboss.org/browse/JBTIS-295 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: testing > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > > Talking with [~rcernich] he was interested in doing testing of already packaged bundles on a packaged eclipse. > [~mickael_istria] did this feature for tycho 0.19 documented at http://wiki.eclipse.org/Tycho/Release_Notes/0.19#Test_Execution > [~rcernich] would this cover you intended use case ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21784) ensure cleanup jobs can handle /pulls/ as well as /builds/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21784?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21784: ---------------------------------- Assignee: Nick Boldt > ensure cleanup jobs can handle /pulls/ as well as /builds/ > ---------------------------------------------------------- > > Key: JBIDE-21784 > URL: https://issues.jboss.org/browse/JBIDE-21784 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.1.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Currently the http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/la... job handles automatic purging of old /builds/ and regeneration of composite*.xml files. > It should also handle /pulls/ folders. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21784) ensure cleanup jobs can handle /pulls/ as well as /builds/

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21784: ---------------------------------- Summary: ensure cleanup jobs can handle /pulls/ as well as /builds/ Key: JBIDE-21784 URL: https://issues.jboss.org/browse/JBIDE-21784 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Affects Versions: 4.3.1.Beta2 Reporter: Nick Boldt Currently the http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-cleanup/la... job handles automatic purging of old /builds/ and regeneration of composite*.xml files. It should also handle /pulls/ folders. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21783) Duplicates of environment variables should be forbidden

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21783: ---------------------------------------- Summary: Duplicates of environment variables should be forbidden Key: JBIDE-21783 URL: https://issues.jboss.org/browse/JBIDE-21783 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Viacheslav Kabanovich Fix For: 4.3.1.CR1 On 2nd wizard page of Deploy docker image is a table containing env. variables passed to OpenShift deployment config when docker image is deployed. Currently it is allowed to create duplicates of environment variables (more variables with same name), but only the last one is processed = it is passed to deployment config. E.g. I created env. vars. envvar1=val1 and envvar1=val2, but in deployment config only val2 is located. We should forbidden created duplicates of environment variables with same name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21764) Duplicates of environment variables should be forbidden

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21764?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21764: ------------------------------------------ thanks! cherry-picked to jbosstools-4.3.x > Duplicates of environment variables should be forbidden > ------------------------------------------------------- > > Key: JBIDE-21764 > URL: https://issues.jboss.org/browse/JBIDE-21764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > > On 2nd wizard page of Deploy docker image is a table containing env. variables passed to OpenShift deployment config when docker image is deployed. Currently it is allowed to create duplicates of environment variables (more variables with same name), but only the last one is processed = it is passed to deployment config. E.g. I created env. vars. envvar1=val1 and envvar1=val2, but in deployment config only val2 is located. We should forbidden created duplicates of environment variables with same name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21783) Duplicates of environment variables should be forbidden

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21783?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21783: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Duplicates of environment variables should be forbidden > ------------------------------------------------------- > > Key: JBIDE-21783 > URL: https://issues.jboss.org/browse/JBIDE-21783 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > On 2nd wizard page of Deploy docker image is a table containing env. variables passed to OpenShift deployment config when docker image is deployed. Currently it is allowed to create duplicates of environment variables (more variables with same name), but only the last one is processed = it is passed to deployment config. E.g. I created env. vars. envvar1=val1 and envvar1=val2, but in deployment config only val2 is located. We should forbidden created duplicates of environment variables with same name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21087) Manage Project dialog reorganizes the project list after deleting project

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21087?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21087: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Manage Project dialog reorganizes the project list after deleting project > ------------------------------------------------------------------------- > > Key: JBIDE-21087 > URL: https://issues.jboss.org/browse/JBIDE-21087 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.1.CR1 > > > Deleting a project using the Manage Project dialog causes the table to refresh and project are randomly sorted. We should sort the projects by name as they appear in the table so the view is consistent between operations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21764) Duplicates of environment variables should be forbidden

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21764?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21764: ------------------------------------------ [~scabanovich] looking > Duplicates of environment variables should be forbidden > ------------------------------------------------------- > > Key: JBIDE-21764 > URL: https://issues.jboss.org/browse/JBIDE-21764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > On 2nd wizard page of Deploy docker image is a table containing env. variables passed to OpenShift deployment config when docker image is deployed. Currently it is allowed to create duplicates of environment variables (more variables with same name), but only the last one is processed = it is passed to deployment config. E.g. I created env. vars. envvar1=val1 and envvar1=val2, but in deployment config only val2 is located. We should forbidden created duplicates of environment variables with same name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21751) Sort project in manage project dialog

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21751?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-21751: ---------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.4.0.Alpha1) > Sort project in manage project dialog > ------------------------------------- > > Key: JBIDE-21751 > URL: https://issues.jboss.org/browse/JBIDE-21751 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.1.CR1 > > > The manage project dialog randomly sorts the table of projects. Add sorting in the following order: > 1. default > 2. openshift* > 3. alphabetical by remaining project name -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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