June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4993) Organize feature pack code to facilitate separate EE 8 and EE 9 variants

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-4993?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-4993: ------------------------------------- Description: Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well. > Organize feature pack code to facilitate separate EE 8 and EE 9 variants > ------------------------------------------------------------------------ > > Key: WFCORE-4993 > URL: https://issues.redhat.com/browse/WFCORE-4993 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > Fix For: 13.0.0.Beta1 > > > Separate feature pack code for EE 8 API modules and other modules we may not want in a EE 9 feature pack from the others. > See if the maven dependency set from those two sections can be used by both the legacy feature pack and the galleon feature pack, thus eliminating the duplication of dependency declaration we currently have. > License.xml generation will likely require https://github.com/wildfly/maven-plugins/issues/10 as the split would mean the input would be split as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4993) Organize feature pack code to facilitate separate EE 8 and EE 9 variants

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4993: ---------------------------------------- Summary: Organize feature pack code to facilitate separate EE 8 and EE 9 variants Key: WFCORE-4993 URL: https://issues.redhat.com/browse/WFCORE-4993 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 13.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13567) Disable MPScriptTestCase in the 'alt-dist' test jobs

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13567?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-13567: --------------------------------------- Assignee: (was: Brian Stansberry) > Disable MPScriptTestCase in the 'alt-dist' test jobs > ---------------------------------------------------- > > Key: WFLY-13567 > URL: https://issues.redhat.com/browse/WFLY-13567 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Brian Stansberry > Priority: Minor > Fix For: 21.0.0.Beta1 > > > The 'alt-dist' jobs like https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 configure the TS to use the output of the ee-build/ee-dist modules or to provision using the wildfly-ee FP. MPScriptTestCase can't pass in such a scenario as the enable-microprofile.cli script it wants to run does not exist. So use a JUnit Assume to disable it. Checking for -Dtestsuite.default.build.project.prefix=ee- would probably do the trick. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13567) Disable MPScriptTestCase in the 'alt-dist' test jobs

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13567: --------------------------------------- Summary: Disable MPScriptTestCase in the 'alt-dist' test jobs Key: WFLY-13567 URL: https://issues.redhat.com/browse/WFLY-13567 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 21.0.0.Beta1 The 'alt-dist' jobs like https://ci.wildfly.org/viewType.html?buildTypeId=WF_MasterLinuxAltDistJdk8 configure the TS to use the output of the ee-build/ee-dist modules or to provision using the wildfly-ee FP. MPScriptTestCase can't pass in such a scenario as the enable-microprofile.cli script it wants to run does not exist. So use a JUnit Assume to disable it. Checking for -Dtestsuite.default.build.project.prefix=ee- would probably do the trick. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10173) EjbInvocationStatisticsTestCase fails on Windows: wait-time=0

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-10173?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFLY-10173: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/13314, https://github.com/wildfly/wildfly/pull/13346 (was: https://github.com/wildfly/wildfly/pull/13314) > EjbInvocationStatisticsTestCase fails on Windows: wait-time=0 > ------------------------------------------------------------- > > Key: WFLY-10173 > URL: https://issues.redhat.com/browse/WFLY-10173 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 12.0.0.Final > Reporter: Jan Kalina > Assignee: Cheng Fang > Priority: Major > Fix For: 20.0.0.Final > > > Sometime, when running EjbInvocationStatisticsTestCase on Windows, assertion fails, as wait-time is 0 (verified it is 0 by adding debug message). > For me it fails allTests in most of cases, but when running test standalone, it fails only in 1 of 4 cases. > I suppose it is because of too short sleep in AbstractManagedBean. (in test is called 4 times, each invocation include 50ms sleep, so I consider probable the wait-time is 0 - need to use longer sleeps to fulfill the test) > {code} > [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.078 s <<< FAILURE! - in org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase > [ERROR] testSingletonWaitTime(org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase) Time elapsed: 0.438 s <<< FAILURE! > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.validateWaitTimeStatistic(EjbInvocationStatisticsTestCase.java:179) > at org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.testSingletonWaitTime(EjbInvocationStatisticsTestCase.java:148) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:564) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.jboss.arquillian.junit.Arquillian$8$1.invoke(Arquillian.java:379) > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5291: ------------------------------- Story Points: 1 > Import of empty scesim file leads to Unexpected error > ----------------------------------------------------- > > Key: DROOLS-5291 > URL: https://issues.redhat.com/browse/DROOLS-5291 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.36.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools, kogito-tooling > Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png > > > If user generate a scesim file using vs code extention it is not comparable with BC. > Use Vscode generated files [^Traffic.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5223) User cannot open malformed scesim file. Loading popup is spining infinitive times

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5223?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5223: ------------------------------- Story Points: 1 > User cannot open malformed scesim file. Loading popup is spining infinitive times > --------------------------------------------------------------------------------- > > Key: DROOLS-5223 > URL: https://issues.redhat.com/browse/DROOLS-5223 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.33.0.Final, 7.34.0.Final, 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Traffic.scesim > > > If user import Scesim file that have xml tag unclosed, > then user gets warning, but loading popup is not disappearing > and user cannot proceed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5291) Import of empty scesim file leads to Unexpected error

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5291?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5291: ------------------------------- Sprint: 2020 Week 22-24 (from May 25) > Import of empty scesim file leads to Unexpected error > ----------------------------------------------------- > > Key: DROOLS-5291 > URL: https://issues.redhat.com/browse/DROOLS-5291 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.36.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools, kogito-tooling > Attachments: Traffic.zip, errorlog.txt, image-2020-04-17-16-47-29-261.png, image-2020-04-17-16-47-32-047.png > > > If user generate a scesim file using vs code extention it is not comparable with BC. > Use Vscode generated files [^Traffic.zip] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5223) User cannot open malformed scesim file. Loading popup is spining infinitive times

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5223?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5223: ------------------------------- Sprint: 2020 Week 22-24 (from May 25) > User cannot open malformed scesim file. Loading popup is spining infinitive times > --------------------------------------------------------------------------------- > > Key: DROOLS-5223 > URL: https://issues.redhat.com/browse/DROOLS-5223 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.33.0.Final, 7.34.0.Final, 7.35.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: Traffic.scesim > > > If user import Scesim file that have xml tag unclosed, > then user gets warning, but loading popup is not disappearing > and user cannot proceed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13566) Ensure that Jandex indexes are released from JPA deployment memory after deployment completes

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13566?page=com.atlassian.jira.plugi... ] Scott Marlow updated WFLY-13566: -------------------------------- Fix Version/s: 21.0.0.Beta1 > Ensure that Jandex indexes are released from JPA deployment memory after deployment completes > --------------------------------------------------------------------------------------------- > > Key: WFLY-13566 > URL: https://issues.redhat.com/browse/WFLY-13566 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.2.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Major > Fix For: 21.0.0.Beta1 > > > org.jboss.as.jpa.service.PersistenceUnitServiceImpl#start() needs to always call pu.setAnnotationIndex(null) to clear the deployment reference to the Jandex Indexes. > Currently without the fix, the Jandex Index will be released at application undeployment time. With the fix, the Jandex Index memory will be released after application deployment is complete. Note that the Jandex Index contains metadata for the application deployment classes and are not needed after deployment is complete. > Note that this problem shouldn't occur when persistence.xml contains: > {code} > <property name="wildfly.jpa.twophasebootstrap" value="false"/> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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

jboss-jira June 2020