December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-360) Incremental compilation: Flawed for Rule Templates

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-360?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-360: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1036842 > Incremental compilation: Flawed for Rule Templates > -------------------------------------------------- > > Key: DROOLS-360 > URL: https://issues.jboss.org/browse/DROOLS-360 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michael Anstis > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation does not add new messages when a Rule Template is updated from being valid to being invalid. Full build with valid Rule Template passes; but Incremental Compilation with updated (and invalid) Rule Template does not lead to any "added" messages. > Updating a Rule Template from invalid to valid does however work. Full build with invalid Rule Template correctly returns error messages and Incremental Compilation with updated (and valid) Rule Template does lead to error message being removed. > Unit tests created (failing one @Ignored). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-360) Incremental compilation: Flawed for Rule Templates

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-360?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-360: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1036842|https://bugzilla.redhat.com/show_bug.cgi?id=1036842] from NEW to ASSIGNED > Incremental compilation: Flawed for Rule Templates > -------------------------------------------------- > > Key: DROOLS-360 > URL: https://issues.jboss.org/browse/DROOLS-360 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michael Anstis > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation does not add new messages when a Rule Template is updated from being valid to being invalid. Full build with valid Rule Template passes; but Incremental Compilation with updated (and invalid) Rule Template does not lead to any "added" messages. > Updating a Rule Template from invalid to valid does however work. Full build with invalid Rule Template correctly returns error messages and Incremental Compilation with updated (and valid) Rule Template does lead to error message being removed. > Unit tests created (failing one @Ignored). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-360) Incremental compilation: Flawed for Rule Templates

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-360?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-360. -------------------------------- Fix Version/s: 6.0.1.Final Resolution: Done > Incremental compilation: Flawed for Rule Templates > -------------------------------------------------- > > Key: DROOLS-360 > URL: https://issues.jboss.org/browse/DROOLS-360 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michael Anstis > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation does not add new messages when a Rule Template is updated from being valid to being invalid. Full build with valid Rule Template passes; but Incremental Compilation with updated (and invalid) Rule Template does not lead to any "added" messages. > Updating a Rule Template from invalid to valid does however work. Full build with invalid Rule Template correctly returns error messages and Incremental Compilation with updated (and valid) Rule Template does lead to error message being removed. > Unit tests created (failing one @Ignored). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-360) Incremental compilation: Flawed for Rule Templates

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-360?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-360: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Incremental compilation: Flawed for Rule Templates > -------------------------------------------------- > > Key: DROOLS-360 > URL: https://issues.jboss.org/browse/DROOLS-360 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michael Anstis > Assignee: Mario Fusco > > Incremental compilation does not add new messages when a Rule Template is updated from being valid to being invalid. Full build with valid Rule Template passes; but Incremental Compilation with updated (and invalid) Rule Template does not lead to any "added" messages. > Updating a Rule Template from invalid to valid does however work. Full build with invalid Rule Template correctly returns error messages and Incremental Compilation with updated (and valid) Rule Template does lead to error message being removed. > Unit tests created (failing one @Ignored). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1112) DataSource marked as Serializable

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Jesper Pedersen commented on JBJCA-1112: ---------------------------------------- Yes, for upstream, with a hack > DataSource marked as Serializable > --------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.21.Final, 1.1.1.Final > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.24.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1957) Upgrade Narayana to 5.0.0.M5

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/WFLY-1957?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved WFLY-1957. ------------------------------------ Resolution: Out of Date > Upgrade Narayana to 5.0.0.M5 > ---------------------------- > > Key: WFLY-1957 > URL: https://issues.jboss.org/browse/WFLY-1957 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Paul Robinson > Assignee: Michael Musgrove > Fix For: 8.0.0.CR1 > > > In particular, needed for the fix to WFLY-1929. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1112) DataSource marked as Serializable

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on JBJCA-1112: ------------------------------------- [~jesper.pedersen] So is the original issue resolved now? > DataSource marked as Serializable > --------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.21.Final, 1.1.1.Final > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.24.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-361) Incremental compilation requires to provide the list of modified files even if not necessary

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-361?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-361: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1036807|https://bugzilla.redhat.com/show_bug.cgi?id=1036807] from NEW to MODIFIED > Incremental compilation requires to provide the list of modified files even if not necessary > -------------------------------------------------------------------------------------------- > > Key: DROOLS-361 > URL: https://issues.jboss.org/browse/DROOLS-361 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation requires to provide the list of the modified files since the last compilation. However this could be error-prone and violates the DRY principle, because this list could be automatically calculated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-361) Incremental compilation requires to provide the list of modified files even if not necessary

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-361?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-361: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1036807|https://bugzilla.redhat.com/show_bug.cgi?id=1036807] from MODIFIED to ASSIGNED > Incremental compilation requires to provide the list of modified files even if not necessary > -------------------------------------------------------------------------------------------- > > Key: DROOLS-361 > URL: https://issues.jboss.org/browse/DROOLS-361 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation requires to provide the list of the modified files since the last compilation. However this could be error-prone and violates the DRY principle, because this list could be automatically calculated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-361) Incremental compilation requires to provide the list of modified files even if not necessary

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-361?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-361: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1036807 > Incremental compilation requires to provide the list of modified files even if not necessary > -------------------------------------------------------------------------------------------- > > Key: DROOLS-361 > URL: https://issues.jboss.org/browse/DROOLS-361 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mario Fusco > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > Incremental compilation requires to provide the list of the modified files since the last compilation. However this could be error-prone and violates the DRY principle, because this list could be automatically calculated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 December 2013