January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25050) Prepare windows image with hyperv

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25050?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25050: ---------------------------------- Fix Version/s: 4.5.x (was: 4.5.2.Final) > Prepare windows image with hyperv > --------------------------------- > > Key: JBIDE-25050 > URL: https://issues.jboss.org/browse/JBIDE-25050 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.5.1.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: jenkins > Fix For: 4.5.x > > Attachments: error.log > > > Prepare windows-based images with hyperv allowed and capable of running cdk in Central-ci and add new jenkins label. > * Provision win10-x64-jbds (as some changes were made to jbds script) > * Install manually HyperV in fresh windows image > * Add new virtual switch > * Set env. variable HYPERV_VIRTUAL_SWITCH > * Add user into Hyper-V Administrators group > * Test whether cdk can be run on the slave -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25438: ---------------------------------- Fix Version/s: 4.5.x (was: 4.5.2.Final) > Refactor CDK itests to be more stable against CDK starts that fail sometimes > ---------------------------------------------------------------------------- > > Key: JBIDE-25438 > URL: https://issues.jboss.org/browse/JBIDE-25438 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.3.AM1 > > > Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. > * repair discovery itests > * finish adding of mocking cdk binaries in unsupported cdk versions > * update suites to run faster test classes > * remove deprecated test cases > * think of skipping registration and adding one test case that will start cdk with registration > * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations > Issues to be addressed or incidents that cause fail of job run: > * CDK-216 > * JBIDE-25443 > * https://status.redhat.com/incidents/s7tzh47440f5 > * JBIDE-25446 > * CDK-220 (cdk-3.3.0) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25378) Add cdk itests for multiple server adapters using minishift profile feature

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25378?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25378: ---------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.2.Final) > Add cdk itests for multiple server adapters using minishift profile feature > --------------------------------------------------------------------------- > > Key: JBIDE-25378 > URL: https://issues.jboss.org/browse/JBIDE-25378 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests > Affects Versions: 4.5.1.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: cdk, cdk_server_adapter > Fix For: 4.5.3.AM1 > > > Implement base scenarios for CDK 3.2+ server adapter's profile feature that would include work with two server adapters. https://docs.openshift.org/latest/minishift/using/profiles.html > Test cases can be derived from https://issues.jboss.org/browse/JBIDE-25055. This jira will cover 2nd and 3rd use case. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25438: ---------------------------------- Fix Version/s: 4.5.3.AM1 (was: 4.5.x) > Refactor CDK itests to be more stable against CDK starts that fail sometimes > ---------------------------------------------------------------------------- > > Key: JBIDE-25438 > URL: https://issues.jboss.org/browse/JBIDE-25438 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.3.AM1 > > > Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. > * repair discovery itests > * finish adding of mocking cdk binaries in unsupported cdk versions > * update suites to run faster test classes > * remove deprecated test cases > * think of skipping registration and adding one test case that will start cdk with registration > * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations > Issues to be addressed or incidents that cause fail of job run: > * CDK-216 > * JBIDE-25443 > * https://status.redhat.com/incidents/s7tzh47440f5 > * JBIDE-25446 > * CDK-220 (cdk-3.3.0) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25596) Wrong Git repo used when creating OpenShift application

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-25596: ---------------------------------- Summary: Wrong Git repo used when creating OpenShift application Key: JBIDE-25596 URL: https://issues.jboss.org/browse/JBIDE-25596 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.2.Final Reporter: Jeff MAURY Assignee: Dmitrii Bocharov Fix For: 4.5.x When creating an OpenShift application from a local Eclipse project, the Git repo URL is wrongly extracted. I have clone a project so I have two remotes in my Git config: upstream and orign. I have created a branch and pushed to origin. When the OpenShift application is created, the Git repo URL is upstream and the Git ref is the newly created branch. Thus this is invalid as the newly created branch does not exists on upstream and I would expect the Git repo URL to be origin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25595) Job examples.javaee.it.weekly consumes all the space on device

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25595?page=com.atlassian.jira.plugi... ] Vojtech Prusa commented on JBIDE-25595: --------------------------------------- https://github.com/javaee-samples/javaee7-samples/pull/426 > Job examples.javaee.it.weekly consumes all the space on device > -------------------------------------------------------------- > > Key: JBIDE-25595 > URL: https://issues.jboss.org/browse/JBIDE-25595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, qa > Affects Versions: 4.5.2.Final > Reporter: Ondrej Dockal > Assignee: Vojtech Prusa > > {code} > [hudson@rhel7-x64-1482 javaee7-samples-master]$ pwd > /mnt/hudson_workspace/workspace/examples.javaee.it.weekly/jdk/openjdk-1.8/label/rhel7/jbosstools-integration-tests/tests/org.jboss.tools.examples.ui.bot.test/target/javaee7-samples-master > [hudson@rhel7-x64-1482 javaee7-samples-master]$ du -hs * > 2.3G batch > 3.7G cdi > 616M concurrency > 4.0K Dockerfile > 232K ejb > 154M el > 154M interceptor > 154M jacc > 2.3G jaspic > 154M javamail > 4.1G jaxrs > 308M jaxws > 308M jca > 616M jms > 4.3G jpa > 2.8G jsf > 616M json > 462M jta > 40K LICENSE > 72K pom.xml > 16K README.md > 2.9G servlet > 136K test-utils > 154M util > 308M validation > 4.4G websocket > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25595) Job examples.javaee.it.weekly consumes all the space on device

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25595?page=com.atlassian.jira.plugi... ] Vojtech Prusa updated JBIDE-25595: ---------------------------------- Comment: was deleted (was: https://github.com/javaee-samples/javaee7-samples/pull/426) > Job examples.javaee.it.weekly consumes all the space on device > -------------------------------------------------------------- > > Key: JBIDE-25595 > URL: https://issues.jboss.org/browse/JBIDE-25595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, qa > Affects Versions: 4.5.2.Final > Reporter: Ondrej Dockal > Assignee: Vojtech Prusa > > {code} > [hudson@rhel7-x64-1482 javaee7-samples-master]$ pwd > /mnt/hudson_workspace/workspace/examples.javaee.it.weekly/jdk/openjdk-1.8/label/rhel7/jbosstools-integration-tests/tests/org.jboss.tools.examples.ui.bot.test/target/javaee7-samples-master > [hudson@rhel7-x64-1482 javaee7-samples-master]$ du -hs * > 2.3G batch > 3.7G cdi > 616M concurrency > 4.0K Dockerfile > 232K ejb > 154M el > 154M interceptor > 154M jacc > 2.3G jaspic > 154M javamail > 4.1G jaxrs > 308M jaxws > 308M jca > 616M jms > 4.3G jpa > 2.8G jsf > 616M json > 462M jta > 40K LICENSE > 72K pom.xml > 16K README.md > 2.9G servlet > 136K test-utils > 154M util > 308M validation > 4.4G websocket > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25529) Base New and Noteworthy for 4.5.2.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25529?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25529. ------------------------------ Resolution: Rejected > Base New and Noteworthy for 4.5.2.Final > ----------------------------------------------------- > > Key: JBIDE-25529 > URL: https://issues.jboss.org/browse/JBIDE-25529 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common, foundation, usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.2.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Base JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Base, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Base by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25518 #comment Create N&N for Base 4.5.2.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Base for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.2.Final since the AM3 release of Base, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25542) Visual Editor New and Noteworthy for 4.5.2.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25542?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25542. ------------------------------ Resolution: Rejected > Visual Editor New and Noteworthy for 4.5.2.Final > ----------------------------------------------------- > > Key: JBIDE-25542 > URL: https://issues.jboss.org/browse/JBIDE-25542 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core, visual-page-editor-templates > Reporter: Jeff MAURY > Assignee: Ilya Buziuk > Priority: Critical > Labels: task > Fix For: 4.5.2.Final > > > Ilya Buziuk, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Visual Editor JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Visual Editor, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Visual Editor by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25518 #comment Create N&N for Visual Editor 4.5.2.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Visual Editor for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.2.Final since the AM3 release of Visual Editor, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25543) LiveReload New and Noteworthy for 4.5.2.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25543?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25543. ------------------------------ Resolution: Rejected > LiveReload New and Noteworthy for 4.5.2.Final > ----------------------------------------------------- > > Key: JBIDE-25543 > URL: https://issues.jboss.org/browse/JBIDE-25543 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.2.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed LiveReload JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for LiveReload, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for LiveReload by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25518 #comment Create N&N for LiveReload 4.5.2.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for LiveReload for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.2.Final since the AM3 release of LiveReload, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.2.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.2.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 January 2018