October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-2740) drools-core: Use mojo's antlr-maven-plugin or antlr3-maven-plugin (instead of the antrun plugin with a custom task) so the jar versions are always up to date

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2740?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2740. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > drools-core: Use mojo's antlr-maven-plugin or antlr3-maven-plugin (instead of the antrun plugin with a custom task) so the jar versions are always up to date > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-2740 > URL: https://issues.jboss.org/browse/JBRULES-2740 > Project: JBRULES > Issue Type: Task > Components: drools-core > Affects Versions: 5.1.1.FINAL > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Optional > Fix For: FUTURE > > > - so the jar versions are always up to date > - output to the target directory, as it's generated code and we don't want that in svn. (following antlr maven plugin conventions which following maven's generated code conventions) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3259) Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory."

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3259?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-3259. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > Full build gives a strange warning "[WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory." > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-3259 > URL: https://issues.jboss.org/browse/JBRULES-3259 > Project: JBRULES > Issue Type: Bug > Affects Versions: 5.3.0.Final > Reporter: Toni Rikkola > Assignee: Geoffrey De Smet > Priority: Minor > > Happens on several modules, here is an example of the log: > [INFO] ------------------------------------------------------------------------ > [INFO] Building Drools distribution 5.3.0.Final > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ drools-distribution --- > [INFO] Deleting /Users/rikkola/Codes/drools/drools/drools-distribution/target > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- > [INFO] > [INFO] >>> maven-source-plugin:2.1.2:jar (default) @ drools-distribution >>> > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- > [INFO] > [INFO] <<< maven-source-plugin:2.1.2:jar (default) @ drools-distribution <<< > [INFO] > [INFO] --- maven-source-plugin:2.1.2:jar (default) @ drools-distribution --- > [INFO] > [INFO] >>> maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution >>> > [INFO] > [INFO] --- maven-enforcer-plugin:1.0:enforce (default) @ drools-distribution --- > [INFO] > [INFO] <<< maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution <<< > [INFO] > [INFO] --- maven-source-plugin:2.1.2:test-jar (default) @ drools-distribution --- > [INFO] > [INFO] --- maven-javadoc-plugin:2.7:jar (default) @ drools-distribution --- > [INFO] Not executing Javadoc as the project is not a Java classpath-capable package > [INFO] > [INFO] --- maven-assembly-plugin:2.2.1:single (default) @ drools-distribution --- > [INFO] Reading assembly descriptor: src/main/assembly/assembly-drools.xml > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [WARNING] Cannot include project artifact: org.drools:drools-distribution:pom:5.3.0.Final; it doesn't have an associated file or directory. > [INFO] Copying files to /Users/rikkola/Codes/drools/drools/drools-distribution/target/drools-distribution-5.3.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3520) CamelServerApp.class missing, camel-client.xml wrong for Drools and jBPM integration camel server war on Tomcat

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3520?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-3520. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > CamelServerApp.class missing, camel-client.xml wrong for Drools and jBPM integration camel server war on Tomcat > --------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-3520 > URL: https://issues.jboss.org/browse/JBRULES-3520 > Project: JBRULES > Issue Type: Release > Components: drools-camel > Affects Versions: 5.4.0.CR1, 5.4.0.Final > Environment: Tomcat 6.x > Reporter: Ryley Gahagan > Assignee: Geoffrey De Smet > Priority: Minor > Fix For: 5.4.0.CR1, 5.4.0.Final > > Attachments: CamelServerApp.class, CamelServerApp.java, camel-client.xml > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The CamelServerApp.class file is missing from the war. Also, the camel-client.xml has, as default: > <to uri="cxfrs://http://localhost:8080/drools-server/kservice/rest"/> > <to uri="cxfrs://http://localhost:8080/drools-server/kservice/soap"/> > Which Tomcat deploys out of the box as > <to uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/rest"/> > <to uri="cxfrs://http://localhost:8080/drools-camel-server-5.4.0.Final/kservice/soap"/> > (...5.4.0.CR1 for that dist) > Has existed for awhile, apparently. Documentation indicates test.jsp working out of the box. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2811) Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish the modules in the overview

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2811?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2811. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > Javadocs should aggregate all javadocs of all modules, but should use groups to distinguish the modules in the overview > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBRULES-2811 > URL: https://issues.jboss.org/browse/JBRULES-2811 > Project: JBRULES > Issue Type: Task > Components: drools-api > Affects Versions: 5.1.1.FINAL > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Optional > Fix For: FUTURE > > > Aggregate: > http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html > Groups: > http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#gr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-1917) JBRMS does not support business rules with non ascii characters

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-1917?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-1917. --------------------------------------- Resolution: Out of Date This issue is out of date and discarded. If you disagree, feel free to reopen this issue in the DROOLS, OPTAPLANNER or JBPM jira projects. > JBRMS does not support business rules with non ascii characters > --------------------------------------------------------------- > > Key: JBRULES-1917 > URL: https://issues.jboss.org/browse/JBRULES-1917 > Project: JBRULES > Issue Type: Bug > Affects Versions: 4.0.7 > Reporter: Gregory Chazalon > Assignee: Geoffrey De Smet > Attachments: drools-latin-rule-support.zip > > > A very simple rule containing some Latin1 characters (e.g. 'é', 'à'..), is not compiled correctly when using the JBRMS web app. > The exact same rule defined in a DRL file, and compiled with the drools compiler API is well handled (no characters mismatch). > Actually, the rule defined both ways is : > rule "latin_message" > when > Let information message > then > information message containing latin characters léger problème à résoudre hôpital > end > I strongly suspect a poor character encoding scheme inside the JBRMS code, but I haven't been able to identify it. > The problem is illustrated by the LatinMessageTest test case, bundled inside the small eclipse project provided. > It has two test methods, one building the rule using the drools compiler API, and the other using a binary package built with JBRMS. > The second one fails as of the poor character encoding suspected inside JBRMS web app. > Any help is appreciated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2020) illegible code snippets in PDF

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2020?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2020. --------------------------------------- Resolution: Done Fixed when we moved to asciidoc last year. > illegible code snippets in PDF > ------------------------------ > > Key: JBRULES-2020 > URL: https://issues.jboss.org/browse/JBRULES-2020 > Project: JBRULES > Issue Type: Quality Risk > Components: drools-docs > Affects Versions: 5.0.0.CR1 > Environment: n/a > Reporter: Wolfgang Laun > Assignee: Geoffrey De Smet > Priority: Critical > Fix For: 6.0.0.Alpha1 > > Attachments: example.png, jbrules2020.png > > > In the PDF version of the docs, code snippets appear in red print on black backround. > Headache tablets cost money. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2816) Many dependencies are tagged scope provided, while the should probably be default scope with optional=true

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2816?page=com.atlassian.jira.plug... ] Geoffrey De Smet reassigned JBRULES-2816: ----------------------------------------- Assignee: (was: Geoffrey De Smet) > Many dependencies are tagged scope provided, while the should probably be default scope with optional=true > ---------------------------------------------------------------------------------------------------------- > > Key: JBRULES-2816 > URL: https://issues.jboss.org/browse/JBRULES-2816 > Project: JBRULES > Issue Type: Task > Components: All > Affects Versions: 5.1.1.FINAL > Reporter: Geoffrey De Smet > Fix For: 6.0.0.Alpha1 > > > 86 uses of scope provided. 13 usages of optional true. > Normally scope provided is used for JDK, JAva webstart and when deploying to a servlet container, the servlet API... > Targets > String '<scope>provided</scope>' > Found usages (86 usages) > drools (4 usages) > /home/gdesmet/projects/jboss/drools (4 usages) > pom.xml (4 usages) > (968, 9) <scope>provided</scope> > (975, 9) <scope>provided</scope> > (1576, 9) <scope>provided</scope> > (1582, 9) <scope>provided</scope> > drools-api (12 usages) > /home/gdesmet/projects/jboss/drools/drools-api (12 usages) > pom.xml (12 usages) > (18, 7) <scope>provided</scope> > (23, 7) <scope>provided</scope> > (28, 7) <scope>provided</scope> > (33, 7) <scope>provided</scope> > (38, 7) <scope>provided</scope> > (43, 7) <scope>provided</scope> > (48, 7) <scope>provided</scope> > (53, 7) <scope>provided</scope> > (58, 7) <scope>provided</scope> > (63, 7) <scope>provided</scope> > (68, 7) <scope>provided</scope> > (73, 7) <scope>provided</scope> > drools-bpmn2 (2 usages) > /home/gdesmet/projects/jboss/drools/drools-process/drools-bpmn2 (2 usages) > pom.xml (2 usages) > (119, 7) <scope>provided</scope> > (124, 7) <scope>provided</scope> > drools-camel (1 usage) > /home/gdesmet/projects/jboss/drools/drools-camel (1 usage) > pom.xml (1 usage) > (186, 7) <scope>provided</scope> > drools-compiler (7 usages) > /home/gdesmet/projects/jboss/drools/drools-compiler (7 usages) > pom.xml (7 usages) > (23, 7) <scope>provided</scope> > (28, 7) <scope>provided</scope> > (82, 7) <scope>provided</scope> > (87, 7) <scope>provided</scope> > (92, 7) <scope>provided</scope> > (97, 7) <scope>provided</scope> > (102, 7) <scope>provided</scope> > drools-core (7 usages) > /home/gdesmet/projects/jboss/drools/drools-core (7 usages) > pom.xml (7 usages) > (18, 7) <scope>provided</scope> > (23, 7) <scope>provided</scope> > (56, 7) <scope>provided</scope> > (61, 7) <scope>provided</scope> > (66, 7) <scope>provided</scope> > (71, 7) <scope>provided</scope> > (76, 7) <scope>provided</scope> > drools-decisiontables (2 usages) > /home/gdesmet/projects/jboss/drools/drools-decisiontables (2 usages) > pom.xml (2 usages) > (32, 7) <scope>provided</scope> > (37, 7) <scope>provided</scope> > drools-flow-compiler (7 usages) > /home/gdesmet/projects/jboss/drools/drools-flow-compiler (7 usages) > pom.xml (7 usages) > (17, 7) <scope>provided</scope> > (22, 7) <scope>provided</scope> > (42, 7) <scope>provided</scope> > (47, 7) <scope>provided</scope> > (52, 7) <scope>provided</scope> > (57, 7) <scope>provided</scope> > (62, 7) <scope>provided</scope> > drools-flow-core (7 usages) > /home/gdesmet/projects/jboss/drools/drools-flow-core (7 usages) > pom.xml (7 usages) > (17, 7) <scope>provided</scope> > (22, 7) <scope>provided</scope> > (37, 7) <scope>provided</scope> > (42, 7) <scope>provided</scope> > (47, 7) <scope>provided</scope> > (52, 7) <scope>provided</scope> > (57, 7) <scope>provided</scope> > drools-flow-persistence-jpa (4 usages) > /home/gdesmet/projects/jboss/drools/drools-flow-persistence-jpa (4 usages) > pom.xml (4 usages) > (98, 7) <scope>provided</scope> > (103, 7) <scope>provided</scope> > (109, 7) <scope>provided</scope> > (114, 7) <scope>provided</scope> > drools-grid (12 usages) > /home/gdesmet/projects/jboss/drools/drools-grid (3 usages) > pom.xml (3 usages) > (24, 13) <scope>provided</scope> > (29, 13) <scope>provided</scope> > (34, 13) <scope>provided</scope> > /home/gdesmet/projects/jboss/drools/drools-grid/drools-grid-distributed-api (3 usages) > pom.xml (3 usages) > (36, 10) <scope>provided</scope> > (41, 10) <scope>provided</scope> > (46, 10) <scope>provided</scope> > /home/gdesmet/projects/jboss/drools/drools-grid/drools-grid-local (3 usages) > pom.xml (3 usages) > (33, 7) <scope>provided</scope> > (38, 7) <scope>provided</scope> > (43, 7) <scope>provided</scope> > /home/gdesmet/projects/jboss/drools/drools-grid/drools-grid-remote-api (3 usages) > pom.xml (3 usages) > (38, 7) <scope>provided</scope> > (43, 7) <scope>provided</scope> > (48, 7) <scope>provided</scope> > drools-guvnor (5 usages) > /home/gdesmet/projects/jboss/drools/drools-guvnor (5 usages) > pom.xml (5 usages) > (205, 7) <scope>provided</scope> > (222, 7) <scope>provided</scope> > (265, 7) <scope>provided</scope> > (270, 7) <scope>provided</scope> > (296, 7) <scope>provided</scope> > drools-ide-common (1 usage) > /home/gdesmet/projects/jboss/drools/drools-ide-common (1 usage) > pom.xml (1 usage) > (37, 7) <scope>provided</scope> > drools-jsr94 (1 usage) > /home/gdesmet/projects/jboss/drools/drools-jsr94 (1 usage) > pom.xml (1 usage) > (73, 7) <scope>provided</scope> > drools-persistence-jpa (4 usages) > /home/gdesmet/projects/jboss/drools/drools-persistence-jpa (4 usages) > pom.xml (4 usages) > (83, 7) <scope>provided</scope> > (88, 7) <scope>provided</scope> > (94, 7) <scope>provided</scope> > (99, 7) <scope>provided</scope> > drools-spring (2 usages) > /home/gdesmet/projects/jboss/drools/drools-container/drools-spring (2 usages) > pom.xml (2 usages) > (53, 7) <scope>provided</scope> > (59, 7) <scope>provided</scope> > gwt-console-server-drools (8 usages) > /home/gdesmet/projects/jboss/drools/drools-process/drools-gwt-server-war (8 usages) > pom.xml (8 usages) > (46, 7) <scope>provided</scope> > (52, 7) <scope>provided</scope> > (58, 7) <scope>provided</scope> > (64, 7) <scope>provided</scope> > (70, 7) <scope>provided</scope> > (76, 7) <scope>provided</scope> > (82, 7) <scope>provided</scope> > (88, 7) <scope>provided</scope> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-2908) Build: Our parent pom must extend jboss parent pom and do not replicate anything in there

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2908?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2908. --------------------------------------- Resolution: Done Fixed a long time ago > Build: Our parent pom must extend jboss parent pom and do not replicate anything in there > ----------------------------------------------------------------------------------------- > > Key: JBRULES-2908 > URL: https://issues.jboss.org/browse/JBRULES-2908 > Project: JBRULES > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Minor > > <parent> > <groupId>org.jboss</groupId> > <artifactId>jboss-parent</artifactId> > <version>5</version> > </parent> > More info in http://community.jboss.org/wiki/MavenDeployingaSnapshot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3334) Expose number of busy threads in the task worker thread pool via CLI (management API)

by Masafumi Miura (JIRA)

Masafumi Miura created WFCORE-3334: -------------------------------------- Summary: Expose number of busy threads in the task worker thread pool via CLI (management API) Key: WFCORE-3334 URL: https://issues.jboss.org/browse/WFCORE-3334 Project: WildFly Core Issue Type: Feature Request Components: IO Affects Versions: 3.0.4.Final Reporter: Masafumi Miura Assignee: David Lloyd WFLY-8203 / XNIO-283 exposed number of busy threads in the task worker thread pool via JMX. It would be useful to expose the metric via CLI (management API). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3333) Expose number of busy threads in the task worker thread pool via CLI (management API)

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3333?page=com.atlassian.jira.plugi... ] Masafumi Miura updated WFCORE-3333: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2868, https://github.com/wildfly/wildfly-core/pull/2869 (was: https://github.com/wildfly/wildfly-core/pull/2868) > Expose number of busy threads in the task worker thread pool via CLI (management API) > ------------------------------------------------------------------------------------- > > Key: WFCORE-3333 > URL: https://issues.jboss.org/browse/WFCORE-3333 > Project: WildFly Core > Issue Type: Feature Request > Components: IO > Affects Versions: 3.0.4.Final > Reporter: Masafumi Miura > Assignee: David Lloyd > > WFLY-8203 / XNIO-283 exposed number of busy threads in the task worker thread pool via JMX. It would be useful to expose the metric via CLI (management API). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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