September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24731) Add more unit tests for hibernate-search tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24731?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24731: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Add more unit tests for hibernate-search tools > ---------------------------------------------- > > Key: JBIDE-24731 > URL: https://issues.jboss.org/browse/JBIDE-24731 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24592) Study Foreman documentation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24592?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24592: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM2) > Study Foreman documentation > --------------------------- > > Key: JBIDE-24592 > URL: https://issues.jboss.org/browse/JBIDE-24592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci > Fix For: 4.5.x > > > This issue consists of going through foreman documentation, tutorials and manuals. > Afterwards, it could be possible to address another steps in this process. > Docs: > https://www.theforeman.org/manuals/1.15/index.html > https://beryju.org/en/blog/getting-started-foreman-part-1#install_os > http://projects.theforeman.org/issues/432 > https://groups.google.com/forum/#!topic/foreman-users/FP9uTb8TAFY -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24873: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Add management itests to eap jbds compatibility jenkins job > ----------------------------------------------------------- > > Key: JBIDE-24873 > URL: https://issues.jboss.org/browse/JBIDE-24873 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > The EAP team would like us to add this test > org.jboss.tools.as.management.itests > to their compatibility job: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... > details here: EAP7-194 > The test to be added is run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Cc: [~rob.stryker] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24797: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM2) > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc, hibernate, openshift, server > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24797: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc, hibernate, openshift, server > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24779) Starting an OpenShift application seems to lock workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24779?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24779: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM2) > Starting an OpenShift application seems to lock workspace > --------------------------------------------------------- > > Key: JBIDE-24779 > URL: https://issues.jboss.org/browse/JBIDE-24779 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > I have an openshift application starting from the IDE and can see the progress report. For some reason (not IDE related I imagine), it's taking ages. > In the meantimes, I've tried to turn a regular project into a static web project to be able to create a server adapter, but it seems like the OpenShift Start operation is locking the workspace so my change show a "waiting for background job to complete pop-up", which is persisting as the job in the background doesn't complete. > I have the impression that the openshift start job does lock the workspace and prevents many things from being doable. If it's the case, I believe it should be changed to a regular job without any lock so it's not blocking the user. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24779) Starting an OpenShift application seems to lock workspace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24779?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24779: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = 4.5.x > Starting an OpenShift application seems to lock workspace > --------------------------------------------------------- > > Key: JBIDE-24779 > URL: https://issues.jboss.org/browse/JBIDE-24779 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > I have an openshift application starting from the IDE and can see the progress report. For some reason (not IDE related I imagine), it's taking ages. > In the meantimes, I've tried to turn a regular project into a static web project to be able to create a server adapter, but it seems like the OpenShift Start operation is locking the workspace so my change show a "waiting for background job to complete pop-up", which is persisting as the job in the background doesn't complete. > I have the impression that the openshift start job does lock the workspace and prevents many things from being doable. If it's the case, I believe it should be changed to a regular job without any lock so it's not blocking the user. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24873: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.1.AM2) > Add management itests to eap jbds compatibility jenkins job > ----------------------------------------------------------- > > Key: JBIDE-24873 > URL: https://issues.jboss.org/browse/JBIDE-24873 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.5.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > The EAP team would like us to add this test > org.jboss.tools.as.management.itests > to their compatibility job: > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP... > details here: EAP7-194 > The test to be added is run here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Cc: [~rob.stryker] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25013) Refactor integration tests for use with RedDeer 2.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25013?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25013: ------------------------------- Fix Version/s: 4.5.1.AM3 (was: 4.5.1.AM2) > Refactor integration tests for use with RedDeer 2.0 > --------------------------------------------------- > > Key: JBIDE-25013 > URL: https://issues.jboss.org/browse/JBIDE-25013 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.5.1.AM3 > > > A number of integration-tests plugins require reddeer 1.2 and need to be migrated to use 2.0. > {code}** [1] ./plugins/org.jboss.tools.seam.reddeer/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [2] ./tests/org.jboss.tools.central.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [3] ./tests/org.jboss.tools.dummy.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [4] ./tests/org.jboss.tools.eclipsecs.ui.test/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [5] ./tests/org.jboss.tools.examples.ui.bot.test/META-INF/MANIFEST.MF ** > 9:Require-Bundle: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [6] ./tests/org.jboss.tools.freemarker.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [7] ./tests/org.jboss.tools.jsf.ui.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [8] ./tests/org.jboss.tools.maven.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [9] ./tests/org.jboss.tools.openshift.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25013) Refactor integration tests for use with RedDeer 2.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25013?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25013: ------------------------------- Sprint: devex #138 September 2017 (was: devex #137 September 2017) > Refactor integration tests for use with RedDeer 2.0 > --------------------------------------------------- > > Key: JBIDE-25013 > URL: https://issues.jboss.org/browse/JBIDE-25013 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate, integration-tests > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.5.1.AM3 > > > A number of integration-tests plugins require reddeer 1.2 and need to be migrated to use 2.0. > {code}** [1] ./plugins/org.jboss.tools.seam.reddeer/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [2] ./tests/org.jboss.tools.central.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [3] ./tests/org.jboss.tools.dummy.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [4] ./tests/org.jboss.tools.eclipsecs.ui.test/META-INF/MANIFEST.MF ** > 9: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [5] ./tests/org.jboss.tools.examples.ui.bot.test/META-INF/MANIFEST.MF ** > 9:Require-Bundle: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [6] ./tests/org.jboss.tools.freemarker.ui.bot.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)" > ** [7] ./tests/org.jboss.tools.jsf.ui.test/META-INF/MANIFEST.MF ** > 10: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [8] ./tests/org.jboss.tools.maven.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > ** [9] ./tests/org.jboss.tools.openshift.ui.bot.test/META-INF/MANIFEST.MF ** > 11: org.jboss.reddeer.go;bundle-version="[1.2.0,2.0.0)", > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017