[JBoss JIRA] (DROOLS-357) Multiple static initialization makes debugging Maven issues impossible
by Lukáš Petrovický (JIRA)
[ https://issues.jboss.org/browse/DROOLS-357?page=com.atlassian.jira.plugin... ]
Lukáš Petrovický updated DROOLS-357:
------------------------------------
Labels: reported-by-qe (was: )
> Multiple static initialization makes debugging Maven issues impossible
> ----------------------------------------------------------------------
>
> Key: DROOLS-357
> URL: https://issues.jboss.org/browse/DROOLS-357
> Project: Drools
> Issue Type: Enhancement
> Affects Versions: 6.0.0.Final
> Reporter: Lukáš Petrovický
> Assignee: Mario Fusco
> Labels: reported-by-qe
> Fix For: 6.0.1.Final
>
>
> When running kie-ci tests against productized binaries, most of the tests in that module fail with this particular exception (or similar):
> java.lang.NoClassDefFoundError: Could not initialize class org.kie.scanner.MavenRepository
> at org.kie.scanner.KieModuleMavenTest.testKieModulePojoDependencies(KieModuleMavenTest.java:119)
> Turns out, this exception is (through multiple levels of static initialization) actually caused here:
> https://github.com/droolsjbpm/drools/blob/master/kie-ci/src/main/java/org...
> Maven resolution fails, because it cannot find some dependencies in the project being loaded. As a result, the class is never initialized, fast forward two other classes, and you get the above exception. I kindly ask that this behavior be changed in such a way that the original exception bubbles up through the stack - otherwise, the user has no chance to figure out what's going on.
> The issue is a bit tricky to reproduce, as it's directly related to artifacts not being resolvable - but it should, if my understanding of the error is correct, be enough to have a parser error in the POM that's being loaded.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (DROOLS-742) DecisionTableXLSToDecisionTableGuidedConverterTest fails on jdk8
by Lukáš Petrovický (JIRA)
[ https://issues.jboss.org/browse/DROOLS-742?page=com.atlassian.jira.plugin... ]
Lukáš Petrovický updated DROOLS-742:
------------------------------------
Labels: reported-by-qe (was: )
> DecisionTableXLSToDecisionTableGuidedConverterTest fails on jdk8
> ----------------------------------------------------------------
>
> Key: DROOLS-742
> URL: https://issues.jboss.org/browse/DROOLS-742
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 6.2.0.Final
> Reporter: Tibor Zimányi
> Assignee: Michael Anstis
> Priority: Minor
> Labels: reported-by-qe
>
> Failing test is from drools-wb repo.
> Test methods testConditions() and testConditionsIndexedParameters() fails on jdk8.
> XLS files used in these methods contain multiple parameters column (column with more parameters than one). When XLS is parsed, these parameters are transformed into child columns of BRLConditionColumn. In ParameterUtilities class is method extractTemplateKeys. This method extracts params from preprocessed original string from XLS table cell containing parameters. But because the method uses HashSet as return value, the ordering of parameters cannot be determined (in HashSet, the order of items can be different than the order in which the items were inserted).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (DROOLS-854) NullPointerException in KieModuleMetaDataImpl.init
by Lukáš Petrovický (JIRA)
[ https://issues.jboss.org/browse/DROOLS-854?page=com.atlassian.jira.plugin... ]
Lukáš Petrovický updated DROOLS-854:
------------------------------------
Labels: reported-by-qe (was: )
> NullPointerException in KieModuleMetaDataImpl.init
> --------------------------------------------------
>
> Key: DROOLS-854
> URL: https://issues.jboss.org/browse/DROOLS-854
> Project: Drools
> Issue Type: Bug
> Reporter: Zuzka Krejčová
> Assignee: Mario Fusco
> Labels: reported-by-qe
> Fix For: 6.3.0.CR1
>
>
> When creating certain types of assets in the gui, user gets an error modal: "Unable to complete your request. The following exception occurred: null."
> The asset is created, but cannot be loaded (reopening results in the same error).
> It seems that the newly created asset can be loaded after a project build.
> Editors/assets affected are:
> guided rules, guided rule templates, drl, guided score cards, guided dtables, guided decision trees, test scenarios
> (others - enumerations, dsl, process definitions, ... are okay)
> It might not be reproducible with drools-wb (based on irc conversations with [~wmedvede]).
> Server log points to DMO:
> Caused by: java.lang.NullPointerException
> at org.kie.scanner.KieModuleMetaDataImpl.init(KieModuleMetaDataImpl.java:147)
> at org.kie.scanner.KieModuleMetaDataImpl.<init>(KieModuleMetaDataImpl.java:87)
> at org.kie.scanner.KieModuleMetaData$Factory.newKieModuleMetaData(KieModuleMetaData.java:45)
> at org.kie.workbench.common.services.datamodel.backend.server.cache.LRUDataModelOracleCache.loadEnumsForPackage(LRUDataModelOracleCache.java:171)
> Stacktrace to be found at [http://pastebin.test.redhat.com/299022].
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (DROOLS-828) Agenda group clear command doesn't work
by Lukáš Petrovický (JIRA)
[ https://issues.jboss.org/browse/DROOLS-828?page=com.atlassian.jira.plugin... ]
Lukáš Petrovický updated DROOLS-828:
------------------------------------
Labels: reported-by-qe (was: )
> Agenda group clear command doesn't work
> ---------------------------------------
>
> Key: DROOLS-828
> URL: https://issues.jboss.org/browse/DROOLS-828
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Beta1
> Reporter: Karel Suta
> Assignee: Mario Fusco
> Priority: Minor
> Labels: reported-by-qe
>
> Created two rules, one is assigned to agenda group. In test case I set focus to rule in agenda group, clear that agenda group and fire all rules.
> I expected that just rule without agenda group will be executed, but rule with agenda group was executed too.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months
[JBoss JIRA] (DROOLS-934) Persistence unit tests - DB2 default schema not specified
by Lukáš Petrovický (JIRA)
[ https://issues.jboss.org/browse/DROOLS-934?page=com.atlassian.jira.plugin... ]
Lukáš Petrovický updated DROOLS-934:
------------------------------------
Labels: reported-by-qe (was: )
> Persistence unit tests - DB2 default schema not specified
> ---------------------------------------------------------
>
> Key: DROOLS-934
> URL: https://issues.jboss.org/browse/DROOLS-934
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.3.0.Final
> Reporter: Tibor Zimányi
> Assignee: Petr Široký
> Priority: Minor
> Labels: reported-by-qe
> Fix For: 6.4.x
>
>
> Unit tests in drools-persistence-jpa don't work on DB2 database system because there isn't specified DB schema in tests.
> Things needed to be done:
> - hibernate.default_schema property set in persistence.xml
> - schema should be set in PersistenceUtil, when creating data source
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 4 months