September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-234) Release JBoss / Jakarta JASPI 2.0.0.CR2

by Darran Lofthouse (Jira)

Darran Lofthouse created JBEE-234: ------------------------------------- Summary: Release JBoss / Jakarta JASPI 2.0.0.CR2 Key: JBEE-234 URL: https://issues.jboss.org/browse/JBEE-234 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jaspi-api Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR2 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-233) Apply changes from 1.1.3 branch to JASPI

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-233?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-233. ----------------------------------- Resolution: Done > Apply changes from 1.1.3 branch to JASPI > ---------------------------------------- > > Key: JBEE-233 > URL: https://issues.jboss.org/browse/JBEE-233 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-188) [Galleon] Exisiting EAP templates are not able to use chained builds

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFWIP-188?page=com.atlassian.jira.plugin.... ] Jean Francois Denise commented on WFWIP-188: -------------------------------------------- [~mjurc], the <image-build-artifacts> is not required to run the final image. It can be deleted. The issue I am seeing is that user would not have the ability to use the template to create a single legacy build. Ideally it should be configurable but templates don't offer this capability. So if we go the chained build way it would become the only way to go. > [Galleon] Exisiting EAP templates are not able to use chained builds > -------------------------------------------------------------------- > > Key: WFWIP-188 > URL: https://issues.jboss.org/browse/WFWIP-188 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Michal Jurc > Assignee: Jean Francois Denise > Priority: Critical > > It's not possible to trigger a chained build with existing EAP templates. This kind of hinders the usability since the existing templates already cover a lot of useful test cases. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-233) Apply changes from 1.1.3 branch to JASPI

by Darran Lofthouse (Jira)

Darran Lofthouse created JBEE-233: ------------------------------------- Summary: Apply changes from 1.1.3 branch to JASPI Key: JBEE-233 URL: https://issues.jboss.org/browse/JBEE-233 Project: JBoss Enterprise Spec APIs Issue Type: Task Components: jboss-jaspi-api Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR2 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12521) Upgrade jboss-transaction-api_1.3_spec to 2.0.0.Final

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/WFLY-12521?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated WFLY-12521: ------------------------------------ Parent: WFLY-12300 Issue Type: Sub-task (was: Component Upgrade) > Upgrade jboss-transaction-api_1.3_spec to 2.0.0.Final > ----------------------------------------------------- > > Key: WFLY-12521 > URL: https://issues.jboss.org/browse/WFLY-12521 > Project: WildFly > Issue Type: Sub-task > Components: Transactions > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > > Contents are https://github.com/jboss/jboss-jakarta-jta-api/pull/4 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12521) Upgrade jboss-transaction-api_1.3_spec to 2.0.0.Final

by Thomas Jenkinson (Jira)

Thomas Jenkinson created WFLY-12521: --------------------------------------- Summary: Upgrade jboss-transaction-api_1.3_spec to 2.0.0.Final Key: WFLY-12521 URL: https://issues.jboss.org/browse/WFLY-12521 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Thomas Jenkinson Assignee: Thomas Jenkinson Contents are https://github.com/jboss/jboss-jakarta-jta-api/pull/4 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12520) Replace managed executor config's thread-factory attribute with thread-priority

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-12520: -------------------------------------- Summary: Replace managed executor config's thread-factory attribute with thread-priority Key: WFLY-12520 URL: https://issues.jboss.org/browse/WFLY-12520 Project: WildFly Issue Type: Enhancement Components: Concurrency Utilities Reporter: Eduardo Martins Assignee: Eduardo Martins A followup of WFLY-12384, the thread-factory attribute on both managed executor models/configs should be deprecated, and a new optional attribute thread-priority should be added to specify the executor's threads priority instead. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12519) MixedDomainTestSuite might not set version to null in AfterClass method

by Ivan Straka (Jira)

Ivan Straka created WFLY-12519: ---------------------------------- Summary: MixedDomainTestSuite might not set version to null in AfterClass method Key: WFLY-12519 URL: https://issues.jboss.org/browse/WFLY-12519 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 18.0.0.Beta1 Reporter: Ivan Straka Assignee: Ivan Straka In our environment server might not start within a timeout (see MixedDomain710TestSuite fail in [1]). {code:java} java.lang.AssertionError: Slave server-one did not start within 20000 ms at org.junit.Assert.fail(Assert.java:88) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.startSlaveServer(MixedDomainTestSupport.java:166) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSupport.start(MixedDomainTestSupport.java:129) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:157) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:133) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:78) at org.jboss.as.test.integration.domain.mixed.MixedDomainTestSuite.getSupport(MixedDomainTestSuite.java:68) at org.jboss.as.test.integration.domain.mixed.eap710.MixedDomain710TestSuite.initializeDomain(MixedDomain710TestSuite.java:44) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:508) 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.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) {code} If this happens during the initialization phase [here|https://github.com/wildfly/wildfly/blob/18.0.0.Beta1/testsuite/mixed...] support static field is not set. When AfterClass close method is called version is not set to null [here|https://github.com/wildfly/wildfly/blob/18.0.0.Beta1/testsuite/mixed...]. This results to other fails in [1]. Simply because of [this|https://github.com/wildfly/wildfly/blob/18.0.0.Beta1/testsuite/mixed...] - version is supposed to be null but it is not. [1] https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-as-tes... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4511) Fix SONAR PR script

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4511?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4511: ------------------------------- Sprint: 2019 Week 35-37 > Fix SONAR PR script > ------------------- > > Key: DROOLS-4511 > URL: https://issues.jboss.org/browse/DROOLS-4511 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Fix "drools-wb" definition inside pr_jobs.groovy -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4503) "Error" popup report java literal for suggested number

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4503?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4503: ------------------------------- Story Points: 1 > "Error" popup report java literal for suggested number > ------------------------------------------------------ > > Key: DROOLS-4503 > URL: https://issues.jboss.org/browse/DROOLS-4503 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Yeser Amer > Priority: Major > Attachments: ErrorPopup.png, FollowError.png, InsertedValue.png > > > When the expected value for a field is a java long, the error popup reports > "The expected value is '2' but the actual one is '3L'." > !ErrorPopup.png|thumbnail! > That means the java literal is used for the suggested (correct) value, while the inserted value as-is is shown as the one to correct. _Of course it is possible that this apply to all types whose java literal representation is different then "absolute" value._ > This is a little bit inconsistent and confusing, especially for someone not knowing java. > The worst consequence is that when user click "Apply", that literal is put inside the cell, > !InsertedValue.png|thumbnail! > and when sent to server it raise error (because server is expecting a number, not a string) > !FollowError.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.5#713005)

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

jboss-jira September 2019