[JBoss JIRA] (DROOLS-1769) All release branches should be protected from a force push
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1769?page=com.atlassian.jira.plugi... ]
Michael Biarnes Kiefer commented on DROOLS-1769:
------------------------------------------------
Fixed - all needed branches in "important" kie reps are protected now.
Until now there is only the option to protect the branches via github UI.
It seems that if you create a new repository in the kiegroup organization the branches in it are not automatically protected (seen in kie-soup and drls-parser).
Send a mail to github team - so lets wait for an answer.
> All release branches should be protected from a force push
> ----------------------------------------------------------
>
> Key: DROOLS-1769
> URL: https://issues.jboss.org/browse/DROOLS-1769
> Project: Drools
> Issue Type: Enhancement
> Components: build
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> There are 2 ways to protect a GitHub repository/branch from force pushing:
> 1) a backend switch (not available in their UI) to disable force pushing for the entire repo (OLD)
> 2) "protected branches" in the "settings" menu of each repo, in the submenu "branches".
> Some repositories, such as "drools" and "optaplanner", have 1), so all their branches are immune to force pushing.
> Newer repositories, such as "optaplanner-wb" probably don't have 1).
> All repositories seem to have 2) for the following branches: master, 6.4.x, 6.5.x.
> BUT NOT 7.3.x etc. That's wrong: this means optaplanner-wb's 7.3.x branch is not protected against force pushes.
> All release branches (7.0.x, 7.1.x, ...) should be protected against force pushing. This includes future release branches, so the release procedure should be adjusted accordingly.
> We should ask github if there's a way to automatically add all new branches to "protected branches".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1769) All release branches should be protected from a force push
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1769?page=com.atlassian.jira.plugi... ]
Michael Biarnes Kiefer resolved DROOLS-1769.
--------------------------------------------
Resolution: Done
> All release branches should be protected from a force push
> ----------------------------------------------------------
>
> Key: DROOLS-1769
> URL: https://issues.jboss.org/browse/DROOLS-1769
> Project: Drools
> Issue Type: Enhancement
> Components: build
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> There are 2 ways to protect a GitHub repository/branch from force pushing:
> 1) a backend switch (not available in their UI) to disable force pushing for the entire repo (OLD)
> 2) "protected branches" in the "settings" menu of each repo, in the submenu "branches".
> Some repositories, such as "drools" and "optaplanner", have 1), so all their branches are immune to force pushing.
> Newer repositories, such as "optaplanner-wb" probably don't have 1).
> All repositories seem to have 2) for the following branches: master, 6.4.x, 6.5.x.
> BUT NOT 7.3.x etc. That's wrong: this means optaplanner-wb's 7.3.x branch is not protected against force pushes.
> All release branches (7.0.x, 7.1.x, ...) should be protected against force pushing. This includes future release branches, so the release procedure should be adjusted accordingly.
> We should ask github if there's a way to automatically add all new branches to "protected branches".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3347?page=com.atlassian.jira.plugi... ]
Chao Wang commented on WFCORE-3347:
-----------------------------------
There are {{setAlternatives()}} and {{addAlternatives()}}. I think we can add a new {{removeAlternatives (String... alternatives)}} in {{AbstractAttributeDefinitionBuilder}} which allows to remove varargs alternatives, and call {{SimpleAttributeDefinitionBuilder}} create with a basis to customize {{SimpleAttributeDefinition}} creation for such case.
I also noticed there is [AbstractAttributeDefinitionBuilder.removeFlag|https://github.com/wildfly/...]
{code:java}
public BUILDER removeFlag(final AttributeAccess.Flag flag) {
if (!isFlagPresent(flag)) {
return (BUILDER) this; //if not present no need to remove
}
final int length = flags.length;
final AttributeAccess.Flag[] newFlags = new AttributeAccess.Flag[length - 1];
int k = 0;
for (AttributeAccess.Flag flag1 : flags) {
if (flag1 != flag) {
newFlags[k] = flag1;
k++;
}
}
if (k != length - 1) {
flags = newFlags;
}
return (BUILDER) this;
}
{code}
However it only sets newFlags back to flags when k != length - 1. The flag will not be removed due to that if condition. Shouldn't it be {{k == length - 1}} ?
Hi [~brian.stansberry] Do you have any knowledge about intention behind this condition? Is this a valid bug?
> add-content operation of deployment resource contains alternative attributes that doesn't exist
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-3347
> URL: https://issues.jboss.org/browse/WFCORE-3347
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Claudio Miranda
> Assignee: Chao Wang
> Priority: Minor
>
> add-content operation contains "content" attribute,
> {code}
> /deployment=*:read-operation-description(name=add-content)
> {code}
> "content" attribute it is a list of other attributes as: input-stream-index, hash, bytes, url. They themselves contains the alternatives metadata as
> {code}
> "url" => {
> "type" => STRING,
> "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "alternatives" => [
> "input-stream-index",
> "hash",
> "bytes",
> "path",
> "relative-to",
> "empty"
> ],
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> {code}
> But the following attributes doesn't exist: path, relative-to, empty
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9454) SecurityContext not injected
by Mike Kachalov (JIRA)
Mike Kachalov created WFLY-9454:
-----------------------------------
Summary: SecurityContext not injected
Key: WFLY-9454
URL: https://issues.jboss.org/browse/WFLY-9454
Project: WildFly
Issue Type: Bug
Components: CDI / Weld, EE
Affects Versions: 11.0.0.CR1
Reporter: Mike Kachalov
Assignee: Martin Kouba
11:49:28,341 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."foo-1.0.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."foo-1.0.ear".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type SecurityContext with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private com.foo.bar.facade.impl.UserRegisterFacadeImpl.securityContext
it's copy issue WELD-2437
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (JBEE-180) Update all spec artifacts to be compatible with JDK9
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/JBEE-180?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar updated JBEE-180:
-----------------------------
Description:
Currently JBMS fails to create automodule name out of our artifacts as we have version of the spec in the name of the jar.
Elegant solution would be to add Automatic-Module-Name manifest entry to the artifacts.
Biggest question is what name of the module should be.
One of suggestions was that until we have offical EG guidline what module name for such spec jars should be, we could use "beta." prefix to note that this name wont be there to stay.
If spec API is one that is upgradable in JDK itself (such as java.transaction) we should use same name that is already used in JDK.
But before we go on and do that, we should make sure that such jars work with jdk9 at all, as there is already known issue with JTA see http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008779.html for more details.
was:
Currently JBMS fails to create automodule name out of our artifacts as we have version of the spec in the name of the jar.
Elegant solution would be to add Automatic-Module-Name manifest entry to the artifacts.
Biggest question is what name of the module should be.
One of suggestions was that until we have offical EG guidline what module name for such spec jars should be, we could use "beta." prefix to note that this name wont be there to stay.
But before we go on and do that, we should make sure that such jars work with jdk9 at all, as there is already known issue with JTA see http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008779.html for more details.
> Update all spec artifacts to be compatible with JDK9
> ----------------------------------------------------
>
> Key: JBEE-180
> URL: https://issues.jboss.org/browse/JBEE-180
> Project: JBoss JavaEE Spec APIs
> Issue Type: Task
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
>
> Currently JBMS fails to create automodule name out of our artifacts as we have version of the spec in the name of the jar.
> Elegant solution would be to add Automatic-Module-Name manifest entry to the artifacts.
> Biggest question is what name of the module should be.
> One of suggestions was that until we have offical EG guidline what module name for such spec jars should be, we could use "beta." prefix to note that this name wont be there to stay.
> If spec API is one that is upgradable in JDK itself (such as java.transaction) we should use same name that is already used in JDK.
> But before we go on and do that, we should make sure that such jars work with jdk9 at all, as there is already known issue with JTA see http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-July/008779.html for more details.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1769) All feature branches should be protected from a force push
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-1769:
----------------------------------------
Summary: All feature branches should be protected from a force push
Key: DROOLS-1769
URL: https://issues.jboss.org/browse/DROOLS-1769
Project: Drools
Issue Type: Enhancement
Components: build
Reporter: Geoffrey De Smet
Assignee: Michael Biarnes Kiefer
There are 2 ways to protect a GitHub repository/branch from force pushing:
1) a backend switch (not available in their UI) to disable force pushing for the entire repo (OLD)
2) "protected branches" in the "settings" menu of each repo, in the submenu "branches".
Some repositories, such as "drools" and "optaplanner", have 1), so all their branches are immune to force pushing.
Newer repositories, such as "optaplanner-wb" probably don't have 1).
All repositories seem to have 2) for the following branches: master, 6.4.x, 6.5.x.
BUT NOT 7.3.x etc. That's wrong: this means optaplanner-wb's 7.3.x branch is not protected against force pushes.
All release branches (7.0.x, 7.1.x, ...) should be protected against force pushing. This includes future release branches, so the release procedure should be adjusted accordingly.
We should ask github if there's a way to automatically add all new branches to "protected branches".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1769) All release branches should be protected from a force push
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1769?page=com.atlassian.jira.plugi... ]
Geoffrey De Smet updated DROOLS-1769:
-------------------------------------
Summary: All release branches should be protected from a force push (was: All feature branches should be protected from a force push)
> All release branches should be protected from a force push
> ----------------------------------------------------------
>
> Key: DROOLS-1769
> URL: https://issues.jboss.org/browse/DROOLS-1769
> Project: Drools
> Issue Type: Enhancement
> Components: build
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
>
> There are 2 ways to protect a GitHub repository/branch from force pushing:
> 1) a backend switch (not available in their UI) to disable force pushing for the entire repo (OLD)
> 2) "protected branches" in the "settings" menu of each repo, in the submenu "branches".
> Some repositories, such as "drools" and "optaplanner", have 1), so all their branches are immune to force pushing.
> Newer repositories, such as "optaplanner-wb" probably don't have 1).
> All repositories seem to have 2) for the following branches: master, 6.4.x, 6.5.x.
> BUT NOT 7.3.x etc. That's wrong: this means optaplanner-wb's 7.3.x branch is not protected against force pushes.
> All release branches (7.0.x, 7.1.x, ...) should be protected against force pushing. This includes future release branches, so the release procedure should be adjusted accordingly.
> We should ask github if there's a way to automatically add all new branches to "protected branches".
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3347) add-content operation of deployment resource contains alternative attributes that doesn't exist
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3347?page=com.atlassian.jira.plugi... ]
Chao Wang reassigned WFCORE-3347:
---------------------------------
Assignee: Chao Wang
> add-content operation of deployment resource contains alternative attributes that doesn't exist
> -----------------------------------------------------------------------------------------------
>
> Key: WFCORE-3347
> URL: https://issues.jboss.org/browse/WFCORE-3347
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Claudio Miranda
> Assignee: Chao Wang
> Priority: Minor
>
> add-content operation contains "content" attribute,
> {code}
> /deployment=*:read-operation-description(name=add-content)
> {code}
> "content" attribute it is a list of other attributes as: input-stream-index, hash, bytes, url. They themselves contains the alternatives metadata as
> {code}
> "url" => {
> "type" => STRING,
> "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "alternatives" => [
> "input-stream-index",
> "hash",
> "bytes",
> "path",
> "relative-to",
> "empty"
> ],
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> {code}
> But the following attributes doesn't exist: path, relative-to, empty
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1768) unable to resolve method using strict-mode
by gabry.wu gabry.wu (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1768?page=com.atlassian.jira.plugi... ]
gabry.wu gabry.wu closed DROOLS-1768.
-------------------------------------
Release Notes Text: ssss
Resolution: Done
ssss
> unable to resolve method using strict-mode
> ------------------------------------------
>
> Key: DROOLS-1768
> URL: https://issues.jboss.org/browse/DROOLS-1768
> Project: Drools
> Issue Type: Feature Request
> Components: core engine
> Affects Versions: 7.0.0.Final
> Reporter: gabry.wu gabry.wu
> Assignee: Mario Fusco
> Labels: support
> Fix For: 7.0.0.Final
>
> Attachments: 374.drl, session.log
>
>
> when i build drools project in linux ,error occors as flow,but in windows 10,error cannot reproduce
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building shrbank-shrools-riskControl 1.0-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ shrbank-shrools-riskControl ---
> [INFO] Deleting /home/gabry/shrools/project/riskcontrol/target
> [INFO]
> [INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ shrbank-shrools-riskControl ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 19 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ shrbank-shrools-riskControl ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 2 source files to /home/gabry/shrools/project/riskcontrol/target/classes
> [INFO] /home/gabry/shrools/project/riskcontrol/src/main/java/com/shrbank/shrools/riskControl/model/RiskEvent.java: Some input files use unchecked or unsafe operations.
> [INFO] /home/gabry/shrools/project/riskcontrol/src/main/java/com/shrbank/shrools/riskControl/model/RiskEvent.java: Recompile with -Xlint:unchecked for details.
> [INFO]
> [INFO] --- kie-maven-plugin:7.3.0.Final:build (default-build) @ shrbank-shrools-riskControl ---
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-core/7.3.0.Final/drools-core-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.core.io.impl.ResourceFactoryServiceImpl
> [INFO] Adding Service org.drools.core.marshalling.impl.MarshallerProviderImpl
> [INFO] Adding Service org.drools.core.concurrent.ExecutorProviderImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-compiler/7.3.0.Final/drools-compiler-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.compiler.kie.builder.impl.KieServicesImpl
> [INFO] Adding Service org.drools.compiler.builder.impl.KnowledgeBuilderFactoryServiceImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/kie/kie-internal/7.3.0.Final/kie-internal-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.kie.internal.services.KieWeaversImpl
> [INFO] Adding Service org.kie.internal.services.KieBeliefsImpl
> [INFO] Adding Service org.kie.internal.services.KieAssemblersImpl
> [INFO] Adding Service org.kie.internal.services.KieRuntimesImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/kie/kie-ci/7.3.0.Final/kie-ci-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.kie.scanner.KieScannerFactoryServiceImpl
> [INFO] Adding Service org.kie.scanner.MavenClassLoaderResolver
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-decisiontables/7.3.0.Final/drools-decisiontables-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.decisiontable.DecisionTableProviderImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-scorecards/7.3.0.Final/drools-scorecards-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.scorecards.ScoreCardProviderImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-pmml/7.3.0.Final/drools-pmml-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.pmml.pmml_4_2.PMML4Compiler
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/jbpm/jbpm-bpmn2/7.3.0.Final/jbpm-bpmn2-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.jbpm.bpmn2.BPMN2ProcessProviderImpl
> [INFO] Adding Service org.jbpm.bpmn2.xml.XmlProcessDumperFactoryServiceImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/jbpm/jbpm-flow-builder/7.3.0.Final/jbpm-flow-builder-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.jbpm.process.builder.ProcessBuilderFactoryServiceImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/jbpm/jbpm-flow/7.3.0.Final/jbpm-flow-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.jbpm.marshalling.impl.ProcessMarshallerFactoryServiceImpl
> [INFO] Adding Service org.jbpm.process.instance.ProcessRuntimeFactoryServiceImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-workbench-models-guided-dtable/7.3.0.Final/drools-workbench-models-guided-dtable-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.workbench.models.guided.dtable.backend.GuidedDecisionTableProviderImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-workbench-models-guided-template/7.3.0.Final/drools-workbench-models-guided-template-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.workbench.models.guided.template.backend.GuidedRuleTemplateProviderImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-workbench-models-guided-scorecard/7.3.0.Final/drools-workbench-models-guided-scorecard-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.workbench.models.guided.scorecard.backend.GuidedScoreCardProviderImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/optaplanner/optaplanner-core/7.3.0.Final/optaplanner-core-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service +org.optaplanner.core.impl.solver.kie.KieSolverAssemblerService
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/kie/kie-dmn-core/7.3.0.Final/kie-dmn-core-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service +org.kie.dmn.core.weaver.DMNWeaverService
> [INFO] Adding Service +org.kie.dmn.core.assembler.DMNAssemblerService
> [INFO] Adding Service +org.kie.dmn.core.runtime.DMNRuntimeService
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/kie/kie-internal/7.3.0.Final/kie-internal-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.kie.internal.services.KieWeaversImpl
> [INFO] Adding Service org.kie.internal.services.KieBeliefsImpl
> [INFO] Adding Service org.kie.internal.services.KieAssemblersImpl
> [INFO] Adding Service org.kie.internal.services.KieRuntimesImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-core/7.3.0.Final/drools-core-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.core.io.impl.ResourceFactoryServiceImpl
> [INFO] Adding Service org.drools.core.marshalling.impl.MarshallerProviderImpl
> [INFO] Adding Service org.drools.core.concurrent.ExecutorProviderImpl
> [INFO] Loading kie.conf from
> [INFO] Discovered kie.conf url=jar:file:/home/gabry/.m2/repository/org/drools/drools-compiler/7.3.0.Final/drools-compiler-7.3.0.Final.jar!/META-INF/kie.conf
> [INFO] Adding Service org.drools.compiler.kie.builder.impl.KieServicesImpl
> [INFO] Adding Service org.drools.compiler.builder.impl.KnowledgeBuilderFactoryServiceImpl
> [INFO] Adding KieModule from resource: FileResource[file=/home/gabry/shrools/project/riskcontrol/src/main/resources]
> [WARNING] Unable to find pom.properties in /home/gabry/shrools/project/riskcontrol/src/main/resources
> [INFO] Recursed up folders, found and used pom.xml /home/gabry/shrools/project/riskcontrol/pom.xml
> [INFO] KieModule was added: FileKieModule[releaseId=com.shrbank.shrools.riskControl:shrbank-shrools-riskControl:1.0-SNAPSHOT,file=/home/gabry/shrools/project/riskcontrol/src/main/resources]
> [ERROR] Unable to build KieBaseModel:defaultKBase
> Unable to Analyse Expression occurTime >= Utils.addSeconds($con0.occurTime,-3600):
> [Error: unable to resolve method using strict-mode: com.shrbank.shrools.riskControl.model.RiskEvent.Utils()]
> [Near : {... occurTime >= Utils.addSeconds($con0.occurTi ....}]
> ^ : [Rule name='374-PAYMENT_RISK_EXCEPTION_1-1小时内设备上支付次数频繁']
> Unable to Analyse Expression relateEventId != $resList.relateEventId && occurTime >= Utils.addSeconds($con0.occurTime,-3600):
> [Error: unable to resolve method using strict-mode: com.shrbank.shrools.riskControl.model.RiskEvent.Utils()]
> [Near : {... tId && occurTime >= Utils.addSeconds($con0.occurTi ....}]
> ^ : [Rule name='374-PAYMENT_RISK_EXCEPTION_1-1小时内设备上支付次数频繁']
> [ERROR] Message [id=1, kieBase=defaultKBase, level=ERROR, path=374.drl, line=-1, column=0
> text=Unable to Analyse Expression occurTime >= Utils.addSeconds($con0.occurTime,-3600):
> [Error: unable to resolve method using strict-mode: com.shrbank.shrools.riskControl.model.RiskEvent.Utils()]
> [Near : {... occurTime >= Utils.addSeconds($con0.occurTi ....}]
> ^]
> [ERROR] Message [id=2, kieBase=defaultKBase, level=ERROR, path=374.drl, line=-1, column=0
> text=Unable to Analyse Expression relateEventId != $resList.relateEventId && occurTime >= Utils.addSeconds($con0.occurTime,-3600):
> [Error: unable to resolve method using strict-mode: com.shrbank.shrools.riskControl.model.RiskEvent.Utils()]
> [Near : {... tId && occurTime >= Utils.addSeconds($con0.occurTi ....}]
> ^]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4.579 s
> [INFO] Finished at: 2017-10-19T09:26:52+08:00
> [INFO] Final Memory: 60M/1409M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.3.0.Final:build (default-build) on project shrbank-shrools-riskControl: Build failed! -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months