June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2621) Support up to 12 arguments in RHS of executable model

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2621?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2621. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/3d17f6349b196835bb258eeb54fd673... > Support up to 12 arguments in RHS of executable model > ----------------------------------------------------- > > Key: DROOLS-2621 > URL: https://issues.jboss.org/browse/DROOLS-2621 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2622) Support up to 12 arguments in RHS of executable model

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2622: ----------------------------------- Summary: Support up to 12 arguments in RHS of executable model Key: DROOLS-2622 URL: https://issues.jboss.org/browse/DROOLS-2622 Project: Drools Issue Type: Enhancement Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2621) Support up to 12 arguments in RHS of executable model

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2621: ----------------------------------- Summary: Support up to 12 arguments in RHS of executable model Key: DROOLS-2621 URL: https://issues.jboss.org/browse/DROOLS-2621 Project: Drools Issue Type: Enhancement Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3743) Allow to search in the CLI multi-page output

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3743?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3743: ----------------------------------------- Description: It would be nice to allow search of patterns in the CLI multi-page output. Something similar as it is done by "less" command. A very good start point for implementation of this is the "less" implementation in aesh-extensions [1]. *List of keys and actions for the search:* * <number> + ENTER : go to line <number> * SLASH : switch to a search mode input ** ANY KEY : adding the char into search pattern ** ENTER : search the document for the pattern ** UP : move up in the search history ** DOWN : move down in the search history * 'n' : go to next match (if no more matches in the direction say "Pattern not found (press RETURN)") * 'N' : go to prev. match (if no more matches in the direction say "Pattern not found (press RETURN)") * HOME / 'g' : go to start of the document * END / 'G' : go to end of the document [1] https://github.com/aeshell/aesh-extensions/tree/master/aesh/src/main/java... was: It would be nice to allow search of patterns in the CLI multi-page output. Something similar as it is done by "less" command. A very good start point for implementation of this is the "less" implementation in aesh-extensions [1]. *List of keys and actions for the search:* * <number> + ENTER : go to line <number> * SLASH : switch to a search mode input ** ANY KEY : adding the char into search pattern ** ENTER : search the document for the pattern ** UP : move up in the search history ** DOWN : move down in the search history * 'n' : go to next match (if no more matches in the direction say "Pattern not found (press RETURN)") * 'N' : go to prev. match (if no more matches in the direction say "Pattern not found (press RETURN)") * 'j' : go line down * 'k' : go line up * HOME / 'g' : go to start of the document * END / 'G' : go to end of the document [1] https://github.com/aeshell/aesh-extensions/tree/master/aesh/src/main/java... > Allow to search in the CLI multi-page output > -------------------------------------------- > > Key: WFCORE-3743 > URL: https://issues.jboss.org/browse/WFCORE-3743 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Marek Marusic > Assignee: Jean-Francois Denise > > It would be nice to allow search of patterns in the CLI multi-page output. Something similar as it is done by "less" command. A very good start point for implementation of this is the "less" implementation in aesh-extensions [1]. > *List of keys and actions for the search:* > * <number> + ENTER : go to line <number> > * SLASH : switch to a search mode input > ** ANY KEY : adding the char into search pattern > ** ENTER : search the document for the pattern > ** UP : move up in the search history > ** DOWN : move down in the search history > * 'n' : go to next match (if no more matches in the direction say "Pattern not found (press RETURN)") > * 'N' : go to prev. match (if no more matches in the direction say "Pattern not found (press RETURN)") > * HOME / 'g' : go to start of the document > * END / 'G' : go to end of the document > [1] https://github.com/aeshell/aesh-extensions/tree/master/aesh/src/main/java... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3743) Allow to search in the CLI multi-page output

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3743?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-3743: ----------------------------------------- Description: It would be nice to allow search of patterns in the CLI multi-page output. Something similar as it is done by "less" command. A very good start point for implementation of this is the "less" implementation in aesh-extensions [1]. *List of keys and actions for the search:* * SLASH : switch to a search mode input ** ANY KEY : adding the char into search pattern ** ENTER : search the document for the pattern ** UP : move up in the search history ** DOWN : move down in the search history * 'n' : go to next match (if no more matches in the direction say "Pattern not found (press RETURN)") * 'N' : go to prev. match (if no more matches in the direction say "Pattern not found (press RETURN)") * HOME / 'g' : go to start of the document * END / 'G' : go to end of the document [1] https://github.com/aeshell/aesh-extensions/tree/master/aesh/src/main/java... was: It would be nice to allow search of patterns in the CLI multi-page output. Something similar as it is done by "less" command. A very good start point for implementation of this is the "less" implementation in aesh-extensions [1]. *List of keys and actions for the search:* * <number> + ENTER : go to line <number> * SLASH : switch to a search mode input ** ANY KEY : adding the char into search pattern ** ENTER : search the document for the pattern ** UP : move up in the search history ** DOWN : move down in the search history * 'n' : go to next match (if no more matches in the direction say "Pattern not found (press RETURN)") * 'N' : go to prev. match (if no more matches in the direction say "Pattern not found (press RETURN)") * HOME / 'g' : go to start of the document * END / 'G' : go to end of the document [1] https://github.com/aeshell/aesh-extensions/tree/master/aesh/src/main/java... > Allow to search in the CLI multi-page output > -------------------------------------------- > > Key: WFCORE-3743 > URL: https://issues.jboss.org/browse/WFCORE-3743 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI > Reporter: Marek Marusic > Assignee: Jean-Francois Denise > > It would be nice to allow search of patterns in the CLI multi-page output. Something similar as it is done by "less" command. A very good start point for implementation of this is the "less" implementation in aesh-extensions [1]. > *List of keys and actions for the search:* > * SLASH : switch to a search mode input > ** ANY KEY : adding the char into search pattern > ** ENTER : search the document for the pattern > ** UP : move up in the search history > ** DOWN : move down in the search history > * 'n' : go to next match (if no more matches in the direction say "Pattern not found (press RETURN)") > * 'N' : go to prev. match (if no more matches in the direction say "Pattern not found (press RETURN)") > * HOME / 'g' : go to start of the document > * END / 'G' : go to end of the document > [1] https://github.com/aeshell/aesh-extensions/tree/master/aesh/src/main/java... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10524) Support Eclipse MicroProfile Config

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-10524: ---------------------------------- Summary: Support Eclipse MicroProfile Config Key: WFLY-10524 URL: https://issues.jboss.org/browse/WFLY-10524 Project: WildFly Issue Type: Feature Request Reporter: Jeff Mesnil Assignee: Jeff Mesnil Support Eclipse MicroProfile Config for applications deployed in WildFly. The integration uses the smallrye-config component to provide the MicroProfile Config implementation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10523) Upgrade WildFly Core 6.0.0.Alpha1

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-10523: ---------------------------------- Summary: Upgrade WildFly Core 6.0.0.Alpha1 Key: WFLY-10523 URL: https://issues.jboss.org/browse/WFLY-10523 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ] Martin Simka edited comment on WFLY-10520 at 6/7/18 4:59 AM: ------------------------------------------------------------- This should also include configuration option in management model. Existing applications should work without changes, so modifying jboss-deployment-structure.xml isn't option. Question is whether it should enabled or disabled by default. was (Author: simkam): This should also include configuration option in management model. Existing applications should work without changes, so modifying jboss-deployment-structure.xml isn't option. > Add Hibernate ORM 5.3 compatibility transformer > ----------------------------------------------- > > Key: WFLY-10520 > URL: https://issues.jboss.org/browse/WFLY-10520 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Scott Marlow > Fix For: 14.0.0.CR1 > > > A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3913) HTTPSchemeServiceAuthModule contructor is not defined

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3913?page=com.atlassian.jira.plugi... ] Hisanobu Okuda updated WFCORE-3913: ----------------------------------- Attachment: test.war > HTTPSchemeServiceAuthModule contructor is not defined > ----------------------------------------------------- > > Key: WFCORE-3913 > URL: https://issues.jboss.org/browse/WFCORE-3913 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.10.Final > Environment: - EAP7.1.0 > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > Attachments: test.war > > > JASPI does not work, since HTTPSchemeServiceAuthModule contructor is not defined. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10520) Add Hibernate ORM 5.3 compatibility transformer

by Martin Simka (JIRA)

[ https://issues.jboss.org/browse/WFLY-10520?page=com.atlassian.jira.plugin... ] Martin Simka commented on WFLY-10520: ------------------------------------- This should also include configuration option in management model. Existing applications should work without changes, so modifying jboss-deployment-structure.xml isn't option. > Add Hibernate ORM 5.3 compatibility transformer > ----------------------------------------------- > > Key: WFLY-10520 > URL: https://issues.jboss.org/browse/WFLY-10520 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Gail Badner > Assignee: Scott Marlow > Fix For: 14.0.0.CR1 > > > A compatibility transformer needs to be added to address Hibernate ORM 5.3 API methods that are no longer compatible with 5.1. -- 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 June 2018