November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-199) The entire kie build should work on maven 3.1.0 too

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ] Geoffrey De Smet updated DROOLS-199: ------------------------------------ Priority: Critical (was: Major) > The entire kie build should work on maven 3.1.0 too > --------------------------------------------------- > > Key: DROOLS-199 > URL: https://issues.jboss.org/browse/DROOLS-199 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > To reproduce: > - Install maven 3.1.0 > - Run mvn-all.sh clean install -Dfull > Note: Any changes to the pom must still allow them to run with 3.0.5 too. > 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. > So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). > 2) There might be other surprises... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-199) The entire kie build should move maven from 3.0.5 to 3.2.x

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ] Geoffrey De Smet updated DROOLS-199: ------------------------------------ Summary: The entire kie build should move maven from 3.0.5 to 3.2.x (was: The entire kie build should work on maven 3.1.0 too) > The entire kie build should move maven from 3.0.5 to 3.2.x > ---------------------------------------------------------- > > Key: DROOLS-199 > URL: https://issues.jboss.org/browse/DROOLS-199 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > To reproduce: > - Install maven 3.1.0 > - Run mvn-all.sh clean install -Dfull > Note: Any changes to the pom must still allow them to run with 3.0.5 too. > 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. > So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). > 2) There might be other surprises... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-199) The entire kie build should work on maven 3.1.0 too

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-199: ----------------------------------------- @mbiarnes For kie 6.3, we should move to maven 3.2.x to avoid known issues in the very old maven version that we're using now. This means: - enforcing at least 3.2.3 (because 3.2.2 has a nasty bug) - notifying our developers in advance This doesn't apply to kie 6.2, because productization's infrastructure isn't ready. Productization has been warned today that this will happen for kie 6.3, so they can prepare for this for 6.3. > The entire kie build should work on maven 3.1.0 too > --------------------------------------------------- > > Key: DROOLS-199 > URL: https://issues.jboss.org/browse/DROOLS-199 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > > To reproduce: > - Install maven 3.1.0 > - Run mvn-all.sh clean install -Dfull > Note: Any changes to the pom must still allow them to run with 3.0.5 too. > 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. > So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). > 2) There might be other surprises... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-163) add-user only escaping first occurrence of special characters

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-163?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-163: ------------------------------------------------ Josef Cacek <jcacek(a)redhat.com> changed the Status of [bug 1150020|https://bugzilla.redhat.com/show_bug.cgi?id=1150020] from ON_QA to VERIFIED > add-user only escaping first occurrence of special characters > ------------------------------------------------------------- > > Key: WFCORE-163 > URL: https://issues.jboss.org/browse/WFCORE-163 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha10 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-213) Clean unreferenced items from the content repository

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-213?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-213: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1018026|https://bugzilla.redhat.com/show_bug.cgi?id=1018026] from ON_QA to ASSIGNED > Clean unreferenced items from the content repository > ---------------------------------------------------- > > Key: WFCORE-213 > URL: https://issues.jboss.org/browse/WFCORE-213 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: 1.0.0.Alpha14 > > > The algorithm for removing unused deployments from the content repository is based on doing this as part of undeploy operation execution. This doesn't cover cases where the content is never explicitly undeployed. For example: > 1) Scanner content that is updated when the server is offline; the old content will not have been "undeployed" during shutdown, and on startup the new content will be installed. > 2) Similar issues with deployments generated from module resources (see "A Mixed Approach on https://community.jboss.org/wiki/ExtendingAS7). When the server shuts down, there is no "subsystem remove" as part of shutdown, so the content added during start will not be removed. > Note that the content repository can include things other than deployments. Currently it also includes management-client-content (specifically rollout plans) and can potentially include anything. This is why it's a "content repository" and not a "deployment repository." The solution for this needs to deal with all cases. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-283) SASL_SERVER and SASL_PROTOCOL options not being passed all the way to Remoting

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-283: --------------------------------------- Summary: SASL_SERVER and SASL_PROTOCOL options not being passed all the way to Remoting Key: WFCORE-283 URL: https://issues.jboss.org/browse/WFCORE-283 Project: WildFly Core Issue Type: Bug Components: Domain Management, Remoting, Security Affects Versions: 1.0.0.Alpha13 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha14 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-282) Wildcard operations that span multiple processes

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFCORE-282?page=com.atlassian.jira.plugin... ] Emanuel Muckenhuber moved WFLY-723 to WFCORE-282: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-282 (was: WFLY-723) Issue Type: Task (was: Feature Request) Component/s: Domain Management (was: Domain Management) Fix Version/s: 1.0.0.Beta1 (was: Awaiting Volunteers) > Wildcard operations that span multiple processes > ------------------------------------------------ > > Key: WFCORE-282 > URL: https://issues.jboss.org/browse/WFCORE-282 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Labels: as7-ignored > Fix For: 1.0.0.Beta1 > > > Handle host=* and host=y,server=* type operations. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-281) Unable to check result "undefined" in cli

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-281?page=com.atlassian.jira.plugin... ] Alexey Loubyansky moved WFLY-4118 to WFCORE-281: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-281 (was: WFLY-4118) Affects Version/s: 1.0.0.Alpha13 (was: 9.0.0.Alpha1) Component/s: CLI (was: CLI) Fix Version/s: (was: 9.0.0.Beta1) > Unable to check result "undefined" in cli > ----------------------------------------- > > Key: WFCORE-281 > URL: https://issues.jboss.org/browse/WFCORE-281 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 1.0.0.Alpha13 > Reporter: Joe Wertz > Assignee: Joe Wertz > Priority: Minor > > if-else constructs in the CLI can't compare against undefined attribute results. > Attempt to create any 'if (result == undefined)' algorithms will always return false. The value-comparison can't handle undefined attributes. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-654) Dynamic update with KieContainer.updateToVersion() not working when ksession was created with config

by Tihomir Meščić (JIRA)

[ https://issues.jboss.org/browse/DROOLS-654?page=com.atlassian.jira.plugin... ] Tihomir Meščić updated DROOLS-654: ---------------------------------- Description: I'm creating my {{KieSession}} by setting {{STREAM}} as the event processing mode in the configuration: {{KieBaseConfiguration config = KieServices.Factory.get()}} {{.newKieBaseConfiguration();}} {{config.setOption(EventProcessingOption.STREAM);}} {{KieContainer kc = ks.newKieContainer( ... releaseId ... );}} {{KieSession ksession = kc.newKieBase(config).newKieSession();}} After that, everything works fine. But when I try to dynamically update to a new version (containing new rules): {{kc.updateToVersion( ... newReleaseId... );}} It seems like all of the facts are removed from the session, and my rules are no longer triggered. When I do not use the configuration object when creating the session and just use: {{KieSession ksession = kc.newKieSession();}} then, everything works as expected. However, this is not an option because I need a way to specify the processing mode as {{STREAM}} (and this is the only way I know of). was: I'm creating my {{KieSession}} by setting {{STREAM}} as the event processing mode in the configuration: {{KieBaseConfiguration config = KieServices.Factory.get()}} {{.newKieBaseConfiguration();}} {{config.setOption(EventProcessingOption.STREAM);}} {{KieContainer kc = ks.newKieContainer( ... releaseId ... );}} {{KieSession ksession = kc.newKieBase(config).newKieSession();}} After that, everything works fine. But when I try to dynamically update to a new version (containing new rules): {{kc.updateToVersion( ... newReleaseId... );}} It seems like all of the facts are removed from the session, and my rules are no longer triggered. When I do not use the configuration object when creating the session and just use: {{KieSession ksession = kc.newKieSession();}} then, everything works as expected, but this is not an option because I need a way to specify the processing mode as {{STREAM}} (and this is the only way I know of). > Dynamic update with KieContainer.updateToVersion() not working when ksession was created with config > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-654 > URL: https://issues.jboss.org/browse/DROOLS-654 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.CR2 > Environment: Ubuntu Linux > Reporter: Tihomir Meščić > Assignee: Mark Proctor > Priority: Blocker > > I'm creating my {{KieSession}} by setting {{STREAM}} as the event processing mode in the configuration: > {{KieBaseConfiguration config = KieServices.Factory.get()}} > {{.newKieBaseConfiguration();}} > {{config.setOption(EventProcessingOption.STREAM);}} > > {{KieContainer kc = ks.newKieContainer( ... releaseId ... );}} > {{KieSession ksession = kc.newKieBase(config).newKieSession();}} > After that, everything works fine. But when I try to dynamically update to a new version (containing new rules): > {{kc.updateToVersion( ... newReleaseId... );}} > It seems like all of the facts are removed from the session, and my rules are no longer triggered. > When I do not use the configuration object when creating the session and just use: > {{KieSession ksession = kc.newKieSession();}} > then, everything works as expected. However, this is not an option because I need a way to specify the processing mode as {{STREAM}} (and this is the only way I know of). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-654) Dynamic update with KieContainer.updateToVersion() not working when ksession was created with config

by Tihomir Meščić (JIRA)

[ https://issues.jboss.org/browse/DROOLS-654?page=com.atlassian.jira.plugin... ] Tihomir Meščić updated DROOLS-654: ---------------------------------- Summary: Dynamic update with KieContainer.updateToVersion() not working when ksession was created with config (was: Dynamic update with KieContainer.updateToVersion() not working in STREAM mode) > Dynamic update with KieContainer.updateToVersion() not working when ksession was created with config > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-654 > URL: https://issues.jboss.org/browse/DROOLS-654 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final, 6.2.0.CR2 > Environment: Ubuntu Linux > Reporter: Tihomir Meščić > Assignee: Mark Proctor > Priority: Blocker > > I'm creating my {{KieSession}} by setting {{STREAM}} as the event processing mode in the configuration: > {{KieBaseConfiguration config = KieServices.Factory.get()}} > {{.newKieBaseConfiguration();}} > {{config.setOption(EventProcessingOption.STREAM);}} > > {{KieContainer kc = ks.newKieContainer( ... releaseId ... );}} > {{KieSession ksession = kc.newKieBase(config).newKieSession();}} > After that, everything works fine. But when I try to dynamically update to a new version (containing new rules): > {{kc.updateToVersion( ... newReleaseId... );}} > It seems like all of the facts are removed from the session, and my rules are no longer triggered. > When I do not use the configuration object when creating the session and just use: > {{KieSession ksession = kc.newKieSession();}} > then, everything works as expected, but this is not an option because I need a way to specify the processing mode as {{STREAM}} (and this is the only way I know of). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 7 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 November 2014