February 2018 - jbosstools-issues

[JBoss JIRA] (JBIDE-25705) central unit test failures in central

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-25705: ---------------------------------- Summary: central unit test failures in central Key: JBIDE-25705 URL: https://issues.jboss.org/browse/JBIDE-25705 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.5.3.AM1 Reporter: Jeff MAURY Assignee: Jeff MAURY Fix For: 4.5.3.AM2 Some unit tests are failing with JDK9 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25629) OpenShift New and Noteworthy for 4.5.3.AM1

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25629?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-25629. --------------------------------- Closing, PR is merged. > OpenShift New and Noteworthy for 4.5.3.AM1 > --------------------------------------------------- > > Key: JBIDE-25629 > URL: https://issues.jboss.org/browse/JBIDE-25629 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.5.3.AM1 > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift 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 OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift 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-25618 #comment Create N&N for OpenShift 4.5.3.AM1 #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 OpenShift for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25643) Reduce number of false-positives in installer/central/rpm tests

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25643?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25643. -------------------------------- > Reduce number of false-positives in installer/central/rpm tests > --------------------------------------------------------------- > > Key: JBIDE-25643 > URL: https://issues.jboss.org/browse/JBIDE-25643 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: install-tests > Affects Versions: 4.5.3.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.3.AM2 > > > Installer tests are usually yellow even if there aren't any real problem. There are two major reasons: > * Remediation page is displayed > ** The Remediation page may be ignored if a nice solution is offered. For example, instead of the installation the componens may be upgraded. > * There is unimportant error in the log > ** e. g. JBDS-4361 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 edited comment on JBIDE-25378 at 2/13/18 4:36 AM: ---------------------------------------------------------------- Verification steps: Use case 1: CDK 3.2+ Server Adapter can be operated (covered by o.j.t.cdk.ui.bot.test.CDK32IntegrationTest) 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift) 3. EXEC: Start/Stop/Restart server adapter 4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) Use case 2: CDK 3.2+ Server Adapter can operate another profile 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift" 3. EXEC: Start/Stop/Restart server adapter 4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift) 3. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift" 4. EXEC: Start default server adapter with default profile 5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) 7. EXEC: Start server adapter with named profile set 8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) 10. EXEC: Stop named profile 11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped 12. EXEC: Stop default profile 13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped was (Author: odockal): Verification steps: Use case 1: CDK 3.2+ Server Adapter can be operated 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift) 3. EXEC: Start/Stop/Restart server adapter 4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) Use case 2: CDK 3.2+ Server Adapter can operate another profile 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift" 3. EXEC: Start/Stop/Restart server adapter 4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift) 3. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift" 4. EXEC: Start default server adapter with default profile 5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) 7. EXEC: Start server adapter with named profile set 8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) 10. EXEC: Stop named profile 11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped 12. EXEC: Stop default profile 13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped > 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, 1 month

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 commented on JBIDE-25378: --------------------------------------- Verification steps: Use case 1: CDK 3.2+ Server Adapter can be operated 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift) 3. EXEC: Start/Stop/Restart server adapter 4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) Use case 2: CDK 3.2+ Server Adapter can operate another profile 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift" 3. EXEC: Start/Stop/Restart server adapter 4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously 1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE 2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift) 3. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift" 4. EXEC: Start default server adapter with default profile 5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) 7. EXEC: Start server adapter with named profile set 8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli) 9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped) 10. EXEC: Stop named profile 11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped 12. EXEC: Stop default profile 13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25699) Could not find artifact org.eclipse.tycho:tycho-packaging-plugin:jar:1.1.0-SNAPSHOT

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25699?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-25699. -------------------------------- > Could not find artifact org.eclipse.tycho:tycho-packaging-plugin:jar:1.1.0-SNAPSHOT > ----------------------------------------------------------------------------------- > > Key: JBIDE-25699 > URL: https://issues.jboss.org/browse/JBIDE-25699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.3.AM1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.3.AM1 > > > {noformat} > [ERROR] Internal error: java.lang.RuntimeException: org.apache.maven.MavenExecutionException: Could not setup plugin ClassRealm: Plugin org.jboss.tools.tycho-plugins:repository-utils:1.1.0-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.eclipse.tycho:tycho-packaging-plugin:jar:1.1.0-SNAPSHOT in central (https://repository.jboss.org/nexus/content/repositories/central/) -> [Help 1] > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25695) Hibernate JDK9 job is broken

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25695?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-25695: -------------------------------------- Job [jbosstools-hibernate-jdk9_master|https://dev-platform-jenkins.rhev-ci-vms...] is still red but the problem mentioned in description seems to be resolved. [~jeffmaury] please close or reopem this issue, thanks. > Hibernate JDK9 job is broken > ---------------------------- > > Key: JBIDE-25695 > URL: https://issues.jboss.org/browse/JBIDE-25695 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: jdk9 > Fix For: 4.5.3.AM1 > > > The hibernate job for JDK9 is broken as unit tests are not run, tries to run tests from sub folder all-tests which does not exist -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1204) List of fixed issues in BPMN2 1.4.2

by Andrej Podhradsky (JIRA)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25700) Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25700?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25700: ------------------------------------- Fix Version/s: 4.5.3.AM2 > Hot deploy of Spring Boot on OpenShift is not working with OpenShift Online > --------------------------------------------------------------------------- > > Key: JBIDE-25700 > URL: https://issues.jboss.org/browse/JBIDE-25700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Aurélien Pupier > Priority: Critical > Labels: online, springboot > Fix For: 4.5.3.AM2 > > > neither with open.paas.redhat.com > so only when using the CDK. > it seems to be due to the fact that the user in the pod are not the same. > Jeff said: > {quote} > For SpringBoot deployments, the application file is called a fat jar and it placed in the /deployments folder (images are upstream fabric8/s2i-java or imagestream redhat-openjdk18-openshift). In order to get live update the file is then unzipped to the /deployments folder leaded to new sub folders BOOT-INF and META-INF > The user permissions on those folders are the following: > /deployments: writable by user jboss and group root > /deployments/BOOT-INF: writable by user jboss readable only by group root > /deployments/META-INF: writable by user jboss readable only by group root > The rsync process with create some sub folders under /deployments/BOOT-INF. The problem that we have is that the user that is assigned for the rsync operation (or when you open a terminal in the OpenShift console) is not jboss (as opposed to Minishift/CDK) and thus we have permissions errors during the rsync operation. > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25704) Update cdk-scripts to work minishift as well

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-25704: ------------------------------------- Summary: Update cdk-scripts to work minishift as well Key: JBIDE-25704 URL: https://issues.jboss.org/browse/JBIDE-25704 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: integration-tests, qa Affects Versions: 4.5.3.AM1 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Priority: Critical Fix For: 4.5.3.AM2 See https://github.com/odockal/cdk-scripts/issues/2. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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