July 2019 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26753) Reverse engineering wrongly overwrites the hibernate.cfg.xml file for hibernate 5.3 and 5.4

by Koen Aers (Jira)

[ https://issues.jboss.org/browse/JBIDE-26753?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-26753: --------------------------------- Assignee: Koen Aers > Reverse engineering wrongly overwrites the hibernate.cfg.xml file for hibernate 5.3 and 5.4 > ------------------------------------------------------------------------------------------- > > Key: JBIDE-26753 > URL: https://issues.jboss.org/browse/JBIDE-26753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.12.0.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > > This issue is related to JBIDE-26569. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new war but wont remove old one

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26746?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26746: ------------------------------- Sprint: devex #169 July 2019, devex #170 Aug 2019 (was: devex #169 July 2019, devex #171 Aug 2019) > Deployment Page: changing location, deploys to new war but wont remove old one > ------------------------------------------------------------------------------ > > Key: JBIDE-26746 > URL: https://issues.jboss.org/browse/JBIDE-26746 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.13.0.AM1 > Reporter: André Dietisheim > Assignee: André Dietisheim > Priority: Major > Labels: deployment_page, server_adapter > Fix For: 4.13.0.AM1 > > > steps: > # EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter > # ASSERT: application is running, server adapter created. > # EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor > # EXEC: start the server adapter > # ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod. > # EXEC: open the application log for the pod > Result: > the new deployment was picked up but failed with an error: > {code} > [0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS > at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) > ... 5 more > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) > at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555) > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555) > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) > at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338) > at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151) > ... 6 more > [0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS > Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}} > [0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT") > [0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT" > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26737) Set up new Jenkins on PSI with use of JCasC

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26737?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26737: ---------------------------------- Fix Version/s: 4.13.0.AM1 (was: 4.13.x) > Set up new Jenkins on PSI with use of JCasC > ------------------------------------------- > > Key: JBIDE-26737 > URL: https://issues.jboss.org/browse/JBIDE-26737 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.x > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: jenkins, quality > Fix For: 4.13.0.AM1 > > > Prepare new jenkins instance to accommodate JCasC configuration for CodeReady Studio team needs. > * -Request instance on PSI- > * Change settings to our repo > * Defined basic workflow -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26737) Set up new Jenkins on PSI with use of JCasC

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26737?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26737: ---------------------------------- Sprint: devex #170 Aug 2019 > Set up new Jenkins on PSI with use of JCasC > ------------------------------------------- > > Key: JBIDE-26737 > URL: https://issues.jboss.org/browse/JBIDE-26737 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.x > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: jenkins, quality > Fix For: 4.13.0.AM1 > > > Prepare new jenkins instance to accommodate JCasC configuration for CodeReady Studio team needs. > * -Request instance on PSI- > * Change settings to our repo > * Defined basic workflow -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26669) Defined basic QE jobs and templates in jenkins-job-dsl repo

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26669?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-26669: ---------------------------------- Sprint: devex #168 June 2019, devex #170 Aug 2019 (was: devex #168 June 2019, devex #169 July 2019 (QE)) > Defined basic QE jobs and templates in jenkins-job-dsl repo > ----------------------------------------------------------- > > Key: JBIDE-26669 > URL: https://issues.jboss.org/browse/JBIDE-26669 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.12.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: dsl, jenkins, jenkins_pipeline, quality > Fix For: 4.13.0.AM1 > > > Continue work on dev-platform/jenkins-dsl-jobs repo and follow best practices as defined in QE - CI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26736) Reduce amount of image used on PSI openstack

by Ondrej Dockal (Jira)

[ https://issues.jboss.org/browse/JBIDE-26736?page=com.atlassian.jira.plugi... ] Ondrej Dockal resolved JBIDE-26736. ----------------------------------- Resolution: Done > Reduce amount of image used on PSI openstack > -------------------------------------------- > > Key: JBIDE-26736 > URL: https://issues.jboss.org/browse/JBIDE-26736 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.13.0.AM1 > > > According to PSI openstack forum docs [1] we should decrease amount of images we use. We should make it to soft/hard limit - 15/20. > [1]: https://docs.google.com/document/d/1w0RsqqdcGYf-9A-wp8fdRa21TJYsK59rEuEBu... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Zbyněk Červinka (Jira)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26750) Update CDI.itests to run on java 11

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26750?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26750: ------------------------------------ Sprint: devex #170 Aug 2019 > Update CDI.itests to run on java 11 > ----------------------------------- > > Key: JBIDE-26750 > URL: https://issues.jboss.org/browse/JBIDE-26750 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Affects Versions: 4.13.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.0.AM1 > > > *Description of the task from [~odockal]:* > As I said some time ago, would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11. Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method? > Let's put it into some utility class, that's an easiest solution. > Update: > I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once. > And you can run test for both server eap and wildfly driven by param in jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26750) Update CDI.itests to run on java 11 and add some parameters to the pom.xml

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26750?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26750: ------------------------------------ Summary: Update CDI.itests to run on java 11 and add some parameters to the pom.xml (was: Update CDI.itests to run on java 11) > Update CDI.itests to run on java 11 and add some parameters to the pom.xml > -------------------------------------------------------------------------- > > Key: JBIDE-26750 > URL: https://issues.jboss.org/browse/JBIDE-26750 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Affects Versions: 4.13.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.0.AM1 > > > *Description of the task from [~odockal]:* > As I said some time ago, would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11. Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method? > Let's put it into some utility class, that's an easiest solution. > Update: > I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once. > And you can run test for both server eap and wildfly driven by param in jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26750) Update CDI.itests to run on java 11

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26750?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26750: ------------------------------------ Story Points: 8 > Update CDI.itests to run on java 11 > ----------------------------------- > > Key: JBIDE-26750 > URL: https://issues.jboss.org/browse/JBIDE-26750 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Affects Versions: 4.13.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.0.AM1 > > > *Description of the task from [~odockal]:* > As I said some time ago, would be awesome to also have test project running on Java 11 in case that test are running on machine with jdk 11. Also, I can see that this condition repeats in every class, do you dare to extract it somewhere else and just call in @requirementResctriction annotated method? > Let's put it into some utility class, that's an easiest solution. > Update: > I can image that server family and version would be parametrized in pom. One could have parameter ie. server.family and server.version and so any update to server and its version could happen in one place at once. > And you can run test for both server eap and wildfly driven by param in jenkins. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 8 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 July 2019