March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10149) Introduce a maximum-timeout management model attribute

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/WFLY-10149?page=com.atlassian.jira.plugin... ] Amos Feng updated WFLY-10149: ----------------------------- Issue Type: Feature Request (was: Enhancement) > Introduce a maximum-timeout management model attribute > ------------------------------------------------------ > > Key: WFLY-10149 > URL: https://issues.jboss.org/browse/WFLY-10149 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Reporter: Amos Feng > Assignee: Amos Feng > > some resources may fail with a timeout value of Integer.MAX_VALUE for various reasons, so a lower "maximum" (such as one year) might be better. The purpose of the suggestion of the maximum timeout attribute would be to make this value configurable (also in the event where someone programmatically sets a timeout which might be problematic), -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10149) Introduce a maximum-timeout management model attribute

by Amos Feng (JIRA)

Amos Feng created WFLY-10149: -------------------------------- Summary: Introduce a maximum-timeout management model attribute Key: WFLY-10149 URL: https://issues.jboss.org/browse/WFLY-10149 Project: WildFly Issue Type: Enhancement Components: Transactions Reporter: Amos Feng Assignee: Amos Feng some resources may fail with a timeout value of Integer.MAX_VALUE for various reasons, so a lower "maximum" (such as one year) might be better. The purpose of the suggestion of the maximum timeout attribute would be to make this value configurable (also in the event where someone programmatically sets a timeout which might be problematic), -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3718) mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3718?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFCORE-3718: ------------------------------------- I have restored https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess to using sed instructions. However, I think this is not a bug in mvn versions plugin. * wildfly-core-parent has *no* dependency on component-matrix (it is listed in the dependencyManagement with a scope import) * component-matrix is a module of wildfly-core-parent * component-matrix parent is org.jboss:jboss-parent while every other modules in core has org.wildfly.core:wildfly-core-parent has a module * component-matrix defines its groupId and version while every other modules in core inherits this value from org.wildfly.core:wildfly-core-parent According to https://www.mojohaus.org/versions-maven-plugin/set-mojo.html, the version is changed for modules only when they have a parent/child relation to the main module (which is not the case for component-matrix). So I think that the mvn versions plugin is right when it does not update the component-matrix as it is not a child of org.wildfly.core:wildfly-core-parent :) If we wanted to use the mvn version plugins, we would have to use mvn versions:set -DnewVersion=XXX -DprocessAllModules=true > mvn versions:set -DnewVersion=xxxx does not replace component-matrix/pom.xml > ---------------------------------------------------------------------------- > > Key: WFCORE-3718 > URL: https://issues.jboss.org/browse/WFCORE-3718 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 5.0.0.Alpha2 > Reporter: Kabir Khan > Assignee: Tomaz Cerar > > {quote} > [2:26 PM] Kabir Khan: @ctomc following https://developer.jboss.org/wiki/WildFlyCoreReleaseProcess, and using > mvn versions:set -DnewVersion=5.0.0.Alpha2 > [2:26 PM] Kabir Khan: it seems to keep component-matrix/pom.xml as -SNAPSHOT > [2:26 PM] Kabir Khan: $git grep "\-SNAPSHOT" > component-matrix/pom.xml: <version>5.0.0.Alpha2-SNAPSHOT</version> > [2:27 PM] Tomaz Cerar: damn, that is not good > [2:27 PM] Tomaz Cerar: versions plugin is bit stupid in some cases > [2:27 PM] Kabir Khan: Should it be in the list of modules? > [2:27 PM] Tomaz Cerar: it is > {quote} > All other versions are correctly replaced. I'd hazard a guess that this also happens in WF full. > CC [~brian.stansberry] - for the 5.0.0.Alpha2 release I'm using the old find/sed way -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1035) CS tool, Error msg with mutually exclusive parameters must contain "really" used option names.

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1035?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev updated ELY-1035: ------------------------------- Comment: was deleted (was: [~hsvabek] Are you ok with closing this issue since this functionality depend on apache commons-cli implementation and the way it handles exclusive options error. Thanks!) > CS tool, Error msg with mutually exclusive parameters must contain "really" used option names. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1035 > URL: https://issues.jboss.org/browse/ELY-1035 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Hynek Švábek > Assignee: Ilia Vassilev > > When we use more mutually exclusive parameters (add, remove) then we get error message. But this message contains only short version of option names. > "r" instead of "remove" > "a" instead of "add" > {code} > [hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary --salt 12345678 --iteration 230 --remove > The option 'r' was specified but an option from this group has already been selected: 'a' > {code} > *Same for "credential-store" command.* -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2438) Drools template : Multiple rows from database map to multiple conditions within the when block of a a single rule

by Rahul Vanimisetty (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2438?page=com.atlassian.jira.plugi... ] Rahul Vanimisetty updated DROOLS-2438: -------------------------------------- Summary: Drools template : Multiple rows from database map to multiple conditions within the when block of a a single rule (was: Drools template : Multiple rows from database within a single rule) > Drools template : Multiple rows from database map to multiple conditions within the when block of a a single rule > ------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-2438 > URL: https://issues.jboss.org/browse/DROOLS-2438 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.6.0.Final > Reporter: Rahul Vanimisetty > Assignee: Mario Fusco > Priority: Blocker > Labels: task > > In a drool template, if i am loading rules from a database, then as per my understanding each row in the database table represents a rule. So a drool template will generate a drl file in the following way : > rule 1 > when > condition(first row of db) > action > rule 2 > condition(2cd row of db) > then > action > etc. > My requirement is to have a dynamic drl generated in the following way : > rule 1 > when > condition 1(1st row of db) > condition 2 (2cd row of db) > condition 3 (3rd row of db) > etc > then > action > end > Please suggest a way to do this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2438) Drools template : Multiple rows from database within a single rule

by Rahul Vanimisetty (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2438?page=com.atlassian.jira.plugi... ] Rahul Vanimisetty updated DROOLS-2438: -------------------------------------- Stackoverflow ID: rahul vanimisetty > Drools template : Multiple rows from database within a single rule > ------------------------------------------------------------------ > > Key: DROOLS-2438 > URL: https://issues.jboss.org/browse/DROOLS-2438 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.6.0.Final > Reporter: Rahul Vanimisetty > Assignee: Mario Fusco > Priority: Blocker > Labels: task > > In a drool template, if i am loading rules from a database, then as per my understanding each row in the database table represents a rule. So a drool template will generate a drl file in the following way : > rule 1 > when > condition(first row of db) > action > rule 2 > condition(2cd row of db) > then > action > etc. > My requirement is to have a dynamic drl generated in the following way : > rule 1 > when > condition 1(1st row of db) > condition 2 (2cd row of db) > condition 3 (3rd row of db) > etc > then > action > end > Please suggest a way to do this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2438) Drools template : Multiple rows from database within a single rule

by Rahul Vanimisetty (JIRA)

Rahul Vanimisetty created DROOLS-2438: ----------------------------------------- Summary: Drools template : Multiple rows from database within a single rule Key: DROOLS-2438 URL: https://issues.jboss.org/browse/DROOLS-2438 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 7.6.0.Final Reporter: Rahul Vanimisetty Assignee: Mario Fusco Priority: Blocker In a drool template, if i am loading rules from a database, then as per my understanding each row in the database table represents a rule. So a drool template will generate a drl file in the following way : rule 1 when condition(first row of db) action rule 2 condition(2cd row of db) then action etc. My requirement is to have a dynamic drl generated in the following way : rule 1 when condition 1(1st row of db) condition 2 (2cd row of db) condition 3 (3rd row of db) etc then action end Please suggest a way to do this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10148) Remove dependency on build tools

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10148?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10148: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3193 > Remove dependency on build tools > -------------------------------- > > Key: WFLY-10148 > URL: https://issues.jboss.org/browse/WFLY-10148 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: David Lloyd > > {quote} > \[2:18 PM\] David Lloyd: can we remove the build tools dependency from wildfly now? > \[2:19 PM\] David Lloyd: I'd like to just inherit the wildfly-core one > \[2:20 PM\] James R. Perkins: I was going to look at that. We should be able to I think. We just need to ensure it's defined in the plugingManagement. > \[2:21 PM\] David Lloyd: it's minor but my modules upgrade is going to conflict with any changes to build tools (in addition to requiring a new build tools) because of it > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3722) WildFly Build Tools version properties is set in two different POMs

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3722?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3722: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3192) > WildFly Build Tools version properties is set in two different POMs > ------------------------------------------------------------------- > > Key: WFCORE-3722 > URL: https://issues.jboss.org/browse/WFCORE-3722 > Project: WildFly Core > Issue Type: Bug > Reporter: David Lloyd > > {noformat} > $ grep build-tools `find . -name pom.xml` > ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3722) WildFly Build Tools version properties is set in two different POMs

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3722?page=com.atlassian.jira.plugi... ] David Lloyd updated WFCORE-3722: -------------------------------- Description: {noformat} $ grep build-tools `find . -name pom.xml` ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> ./pom.xml: <version>${version.org.wildfly.build-tools}</version> ./pom.xml: <version>${version.org.wildfly.build-tools}</version> {noformat} was: {{noformat}} $ grep build-tools `find . -name pom.xml` ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> ./pom.xml: <version>${version.org.wildfly.build-tools}</version> ./pom.xml: <version>${version.org.wildfly.build-tools}</version> {{noformat}} > WildFly Build Tools version properties is set in two different POMs > ------------------------------------------------------------------- > > Key: WFCORE-3722 > URL: https://issues.jboss.org/browse/WFCORE-3722 > Project: WildFly Core > Issue Type: Bug > Reporter: David Lloyd > > {noformat} > $ grep build-tools `find . -name pom.xml` > ./component-matrix/pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version.org.wildfly.build-tools>1.2.6.Final</version.org.wildfly.build-tools> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > ./pom.xml: <version>${version.org.wildfly.build-tools}</version> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2018