March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10107) The artifactId now resolves to quickstart-parent instead of the quickstart name

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10107?page=com.atlassian.jira.plugin... ] Sande Gilda commented on WFLY-10107: ------------------------------------ Removing the BLOCKER since it is an upstream issue only. > The artifactId now resolves to quickstart-parent instead of the quickstart name > ------------------------------------------------------------------------------- > > Key: WFLY-10107 > URL: https://issues.jboss.org/browse/WFLY-10107 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Tomaz Cerar > Fix For: 13.0.0.Beta1 > > > A change to the build broke the README.html generation. > The `artifactId` used to resolve to the specific quickstart name when generating the README.html file from README.adoc. It now generates `quickstart-parent` for all of the quickstarts. > This means you end up with this instruction for the kitchensink quickstart: > This deploys the quickstart-parent/target/quickstart-parent.war to the running instance of the server. > It used to generate: > This deploys the kitchensink/target/kitchensink.war to the running instance of the server. > It is also no longer possible to build an individual quikstart README file. You have to build all of them from the top level. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10107) The artifactId now resolves to quickstart-parent instead of the quickstart name

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/WFLY-10107?page=com.atlassian.jira.plugin... ] Sande Gilda updated WFLY-10107: ------------------------------- Priority: Major (was: Blocker) > The artifactId now resolves to quickstart-parent instead of the quickstart name > ------------------------------------------------------------------------------- > > Key: WFLY-10107 > URL: https://issues.jboss.org/browse/WFLY-10107 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Tomaz Cerar > Fix For: 13.0.0.Beta1 > > > A change to the build broke the README.html generation. > The `artifactId` used to resolve to the specific quickstart name when generating the README.html file from README.adoc. It now generates `quickstart-parent` for all of the quickstarts. > This means you end up with this instruction for the kitchensink quickstart: > This deploys the quickstart-parent/target/quickstart-parent.war to the running instance of the server. > It used to generate: > This deploys the kitchensink/target/kitchensink.war to the running instance of the server. > It is also no longer possible to build an individual quikstart README file. You have to build all of them from the top level. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-85) Jenkins job for building and pushing test-mesh to public Docker Repo

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-85: --------------------------------- Summary: Jenkins job for building and pushing test-mesh to public Docker Repo Key: SWSQE-85 URL: https://issues.jboss.org/browse/SWSQE-85 Project: Swift Sunshine QE Issue Type: QE Task Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10107) The artifactId now resolves to quickstart-parent instead of the quickstart name

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10107?page=com.atlassian.jira.plugin... ] Tomaz Cerar resolved WFLY-10107. -------------------------------- Fix Version/s: 13.0.0.Beta1 Resolution: Done > The artifactId now resolves to quickstart-parent instead of the quickstart name > ------------------------------------------------------------------------------- > > Key: WFLY-10107 > URL: https://issues.jboss.org/browse/WFLY-10107 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Tomaz Cerar > Priority: Blocker > Fix For: 13.0.0.Beta1 > > > A change to the build broke the README.html generation. > The `artifactId` used to resolve to the specific quickstart name when generating the README.html file from README.adoc. It now generates `quickstart-parent` for all of the quickstarts. > This means you end up with this instruction for the kitchensink quickstart: > This deploys the quickstart-parent/target/quickstart-parent.war to the running instance of the server. > It used to generate: > This deploys the kitchensink/target/kitchensink.war to the running instance of the server. > It is also no longer possible to build an individual quikstart README file. You have to build all of them from the top level. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9648) Expose configuration for non-blocking initial state transfer for replicated/distributed caches

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9648?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9648: ------------------------------- Description: A state-transfer with timeout <= 0 should auto-disable awaitInitialTransfer. (was: Additionally, a timeout of zero should auto-disable awaitInitialTransfer.) > Expose configuration for non-blocking initial state transfer for replicated/distributed caches > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9648 > URL: https://issues.jboss.org/browse/WFLY-9648 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > A state-transfer with timeout <= 0 should auto-disable awaitInitialTransfer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9648) Expose configuration for non-blocking initial state transfer for replicated/distributed caches

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9648?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9648: ------------------------------- Affects Version/s: 12.0.0.Final (was: 11.0.0.Final) > Expose configuration for non-blocking initial state transfer for replicated/distributed caches > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9648 > URL: https://issues.jboss.org/browse/WFLY-9648 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Additionally, a timeout of zero should auto-disable awaitInitialTransfer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9648) Expose configuration for non-blocking initial state transfer for replicated/distributed caches

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9648?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9648: ------------------------------- Summary: Expose configuration for non-blocking initial state transfer for replicated/distributed caches (was: Restore ability to disable initial state transfer for replicated/distributed caches) > Expose configuration for non-blocking initial state transfer for replicated/distributed caches > ---------------------------------------------------------------------------------------------- > > Key: WFLY-9648 > URL: https://issues.jboss.org/browse/WFLY-9648 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 12.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Additionally, a timeout of zero should auto-disable awaitInitialTransfer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10090) [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-10090?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFLY-10090: ------------------------------------ [~mnovak] I have debugged the code of the messaging-activemq subsystem that pass the 2 pool size to Artemis and I see that the call to ActiveMQClient.setGlobalThreadPoolProperties uses the expected values at https://github.com/jmesnil/wildfly/blob/WFLY-9407_upgrade_artemis_2.4.0_w... I also noted that the testGlobalPoolsConfiguredBySystemProperty and testGlobalPoolsConfiguredByAttributeInMessagingSubsystem tests passes when they are run separately. Could there be an issue with the way threads are measured (e.g. and accumulated across tests)? > [Artemis 2.x upgrade] Setting globalThreadPool size on client using system properties is ignored > ------------------------------------------------------------------------------------------------ > > Key: WFLY-10090 > URL: https://issues.jboss.org/browse/WFLY-10090 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Priority: Blocker > > Setting client globalThreadPoolSize for configuring max number of ActiveMQ-client-global-threads using system property or in connection factory which is looked up by standalone JMS client is ignored. There is alway 8 * number CPU cores. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10107) The artifactId now resolves to quickstart-parent instead of the quickstart name

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10107?page=com.atlassian.jira.plugin... ] Tomaz Cerar moved JBEAP-14488 to WFLY-10107: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-10107 (was: JBEAP-14488) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Target Release: (was: 7.2.0.CD12.GA) > The artifactId now resolves to quickstart-parent instead of the quickstart name > ------------------------------------------------------------------------------- > > Key: WFLY-10107 > URL: https://issues.jboss.org/browse/WFLY-10107 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Tomaz Cerar > Priority: Blocker > > A change to the build broke the README.html generation. > The `artifactId` used to resolve to the specific quickstart name when generating the README.html file from README.adoc. It now generates `quickstart-parent` for all of the quickstarts. > This means you end up with this instruction for the kitchensink quickstart: > This deploys the quickstart-parent/target/quickstart-parent.war to the running instance of the server. > It used to generate: > This deploys the kitchensink/target/kitchensink.war to the running instance of the server. > It is also no longer possible to build an individual quikstart README file. You have to build all of them from the top level. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2419) Validator fails schema validation for definition xml element with prefix

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2419?page=com.atlassian.jira.plugi... ] Matteo Mortari reassigned DROOLS-2419: -------------------------------------- Assignee: Fedor Gavrilov (was: Matteo Mortari) > Validator fails schema validation for definition xml element with prefix > ------------------------------------------------------------------------ > > Key: DROOLS-2419 > URL: https://issues.jboss.org/browse/DROOLS-2419 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Fedor Gavrilov > Attachments: UsingSemanticNS.dmn > > > Given the attached model and the following test > {code:java} > @Test > public void testTEMP() { > List<DMNMessage> validate = validator.validate(getReader("UsingSemanticNS.dmn"), VALIDATE_SCHEMA, VALIDATE_MODEL, VALIDATE_COMPILATION); > assertThat(ValidatorUtil.formatMessages(validate), validate.size(), is(0)); > } > {code} > fails with: > {code:java} > java.lang.AssertionError: DMNMessage{ severity=ERROR, type=FAILED_XML_VALIDATION, message='Failed XML validation of DMN file: cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', sourceId='null', exception='SAXParseException : cvc-elt.1: Cannot find the declaration of element 'semantic:definitions'.', feelEvent=''} > Expected: is <0> > but: was <1> > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.junit.Assert.assertThat(Assert.java:956) > at org.kie.dmn.validation.ValidatorTest.testTEMP(ValidatorTest.java:92) > ... > {code} -- 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

jboss-jira March 2018