May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1078) Elytron MatchRule.toString() method throws StringIndexOutOfBoundsException

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1078?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1078: ---------------------------------- Fix Version/s: 1.1.0.Beta47 (was: 1.1.0.Beta46) > Elytron MatchRule.toString() method throws StringIndexOutOfBoundsException > -------------------------------------------------------------------------- > > Key: ELY-1078 > URL: https://issues.jboss.org/browse/ELY-1078 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta36 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta47 > > > In case when implementation of {{asString(StringBuilder b)}} for MatchRule does not change length of passed parameter (which is 0) then 'java.lang.StringIndexOutOfBoundsException: String index out of range: -1' is thrown for calling {{MatchRule.toString()}} due to calling {{StringBuilder.setLength(-1)}}. > e.g. MatchRule {{ALL}} in implementation {{asString(StringBuilder b)}} just returns passed parameter, which results to mentioned exception. > Thrown exception: > {code} > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > at java.lang.AbstractStringBuilder.setLength(AbstractStringBuilder.java:180) > at java.lang.StringBuilder.setLength(StringBuilder.java:76) > at org.wildfly.security.auth.client.MatchRule.toString(MatchRule.java:581) > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1188) Release WildFly Elytron 1.1.0.Beta46

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1188?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved ELY-1188. ----------------------------------- Resolution: Done > Release WildFly Elytron 1.1.0.Beta46 > ------------------------------------ > > Key: ELY-1188 > URL: https://issues.jboss.org/browse/ELY-1188 > Project: WildFly Elytron > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta46 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1188) Release WildFly Elytron 1.1.0.Beta46

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1188: ------------------------------------- Summary: Release WildFly Elytron 1.1.0.Beta46 Key: ELY-1188 URL: https://issues.jboss.org/browse/ELY-1188 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta46 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1572) Figure 4.2. Example POM shows old maven group/artifactId

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1572?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1572. --------------------------------- Fix Version/s: 7.1.0.Final Resolution: Done Fixed by https://github.com/kiegroup/kie-docs/commit/307b7487c6c678e2f8a6624185456... > Figure 4.2. Example POM shows old maven group/artifactId > -------------------------------------------------------- > > Key: DROOLS-1572 > URL: https://issues.jboss.org/browse/DROOLS-1572 > Project: Drools > Issue Type: Enhancement > Components: docs > Affects Versions: 6.5.0.Final, 7.0.0.CR3 > Environment: Google Chrome > Reporter: Russell Morrisey > Assignee: Mario Fusco > Fix For: 7.1.0.Final > > > In the Drools documentation, figure 4.2 (*Example project layout and Maven POM*) shows the wrong groupId and artifactId. The correct artifact is: > {code:java} > org.kie:kie-maven-plugin:${runtime.version} > {code} > In addition, the new plugin causes an error in Eclipse unless a section is added to the POM for the eclipse lifecycle-mapping plugin. > https://docs.jboss.org/drools/release/latest/drools-docs/html_single/#_bu... > https://stackoverflow.com/questions/26122801/m2e-connector-for-kie-maven-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1572) Figure 4.2. Example POM shows old maven group/artifactId

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1572?page=com.atlassian.jira.plugi... ] Matteo Mortari commented on DROOLS-1572: ---------------------------------------- Concerning Eclipse, this is normal behaviour of Maven-based project managed from the Eclipse IDE: normally all maven-plugin shall have a corresponding m2e eclipse lifecycle-mapping plugin configuration. This is demonstrated when creating a new project using the Kie archertype, when setting the IDE related flag. The lifecycle-mapping configuration can be left as ignore which is the default, or changed to execution depending on the preferred use case. When the proper Maven build is triggered from the Eclipse IDE, then the Maven build process will use the kie-maven-plugin as expected anyway. > Figure 4.2. Example POM shows old maven group/artifactId > -------------------------------------------------------- > > Key: DROOLS-1572 > URL: https://issues.jboss.org/browse/DROOLS-1572 > Project: Drools > Issue Type: Enhancement > Components: docs > Affects Versions: 6.5.0.Final, 7.0.0.CR3 > Environment: Google Chrome > Reporter: Russell Morrisey > Assignee: Mario Fusco > > In the Drools documentation, figure 4.2 (*Example project layout and Maven POM*) shows the wrong groupId and artifactId. The correct artifact is: > {code:java} > org.kie:kie-maven-plugin:${runtime.version} > {code} > In addition, the new plugin causes an error in Eclipse unless a section is added to the POM for the eclipse lifecycle-mapping plugin. > https://docs.jboss.org/drools/release/latest/drools-docs/html_single/#_bu... > https://stackoverflow.com/questions/26122801/m2e-connector-for-kie-maven-... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1141) KieScanner: add support for listeners

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1141?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1141. --------------------------------- Resolution: Done Implemented with DROOLS-1565 > KieScanner: add support for listeners > ------------------------------------- > > Key: DROOLS-1141 > URL: https://issues.jboss.org/browse/DROOLS-1141 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Marek Winkler > Assignee: Mario Fusco > > For testing purposes, it could be handy to allow user to register listeners to KieScanner. We were thinking about the following events: > - beforeScan > - afterScan > The afterScan method could receive an Event object as a parameter describing what was actually updated during the scan (e.g., what artifacts to which versions?), probably a {{ReleaseId}}? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1099) Couldn't access any web service of drools or kie which run in docker container

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1099?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1099. --------------------------------- Resolution: Cannot Reproduce Bug > Couldn't access any web service of drools or kie which run in docker container > ------------------------------------------------------------------------------ > > Key: DROOLS-1099 > URL: https://issues.jboss.org/browse/DROOLS-1099 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 6.2.0.Final, 6.4.0.CR1 > Environment: Ubuntu 15.04, Docker 1.10.3 > Reporter: Jackey Lee > Assignee: Mario Fusco > Attachments: drools-wb.log, kie-server.log > > > I followed the instructions to run drools and KIE workbenches in docker. But the browser shows "404-Not Found" when I tried to access http://localhost:8080/drools-wb. > It shows "Forbidden" when I tried to access http://localhost:32769/kie-server -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2865) Fix tests that require changes to run with Elytron enabled and the default ManagementRealm removed

by James Perkins (JIRA)

James Perkins created WFCORE-2865: ------------------------------------- Summary: Fix tests that require changes to run with Elytron enabled and the default ManagementRealm removed Key: WFCORE-2865 URL: https://issues.jboss.org/browse/WFCORE-2865 Project: WildFly Core Issue Type: Sub-task Components: Test Suite Reporter: James Perkins Assignee: James Perkins There are a few tests that rely on the default {{ManagementRealm}} to be available. These tests should be fixed to work with Elytron enabled and the default realm removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2748) Move the configuration setup & tests for -Delytron from wildfly to wildfly-core

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2748?page=com.atlassian.jira.plugi... ] Ken Wills commented on WFCORE-2748: ----------------------------------- PR merged here: https://github.com/wildfly-security-incubator/wildfly-core/pull/166 > Move the configuration setup & tests for -Delytron from wildfly to wildfly-core > ------------------------------------------------------------------------------- > > Key: WFCORE-2748 > URL: https://issues.jboss.org/browse/WFCORE-2748 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security, Test Suite > Reporter: Ken Wills > Assignee: Ken Wills > > The current full testsuite performs alternate setup for tests when -Delytron is used prior to executing tests. This configuration should be migrated to core. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1575) Investigate Executable Mode and Rete Build Performance

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1575: ----------------------------------- Summary: Investigate Executable Mode and Rete Build Performance Key: DROOLS-1575 URL: https://issues.jboss.org/browse/DROOLS-1575 Project: Drools Issue Type: Task Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 May 2017