July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1661) KIE-Server-Client needs to be more light-weight

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1661?page=com.atlassian.jira.plugi... ] Duncan Doyle updated DROOLS-1661: --------------------------------- Description: KIE-Server-Client currently drags in a ton of dependencies. A `mnv dependency:tree` gives this output. {code} +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile [INFO] | | +- com.google.guava:guava:jar:20.0:compile [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime {code} So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of `drools-core`optaplanner-persistence-xstream`, etc into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO. It would be nice if we could make this a bit more modular. was: KIE-Server-Client currently drags in a ton of dependencies. A `mnv dependency:tree` gives this output. ``` +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile [INFO] | | +- com.google.guava:guava:jar:20.0:compile [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime ``` So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of `drools-core`optaplanner-persistence-xstream`, etc into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO. It would be nice if we could make this a bit more modular. > KIE-Server-Client needs to be more light-weight > ----------------------------------------------- > > Key: DROOLS-1661 > URL: https://issues.jboss.org/browse/DROOLS-1661 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.1.0.Beta3 > Reporter: Duncan Doyle > Assignee: Edson Tirelli > > KIE-Server-Client currently drags in a ton of dependencies. A `mnv dependency:tree` gives this output. > {code} > +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile > [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile > [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile > [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile > [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile > [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile > [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile > [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile > [INFO] | | +- com.google.guava:guava:jar:20.0:compile > [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile > [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile > [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile > [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile > [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile > [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile > [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile > [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile > [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile > [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile > [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile > [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile > [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile > [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile > [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile > [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile > [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile > [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile > [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile > [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile > [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile > [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile > [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile > [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime > {code} > So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of `drools-core`optaplanner-persistence-xstream`, etc into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO. > It would be nice if we could make this a bit more modular. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1661) KIE-Server-Client needs to be more light-weight

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1661?page=com.atlassian.jira.plugi... ] Duncan Doyle updated DROOLS-1661: --------------------------------- Description: KIE-Server-Client currently drags in a ton of dependencies. A {{mnv dependency:tree}} gives this output: {code} +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile [INFO] | | +- com.google.guava:guava:jar:20.0:compile [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime {code} So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of {{drools-core}}, {{optaplanner-persistence-xstream}}, etc into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO. It would be nice if we could make this a bit more modular. was: KIE-Server-Client currently drags in a ton of dependencies. A `mnv dependency:tree` gives this output. {code} +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile [INFO] | | +- com.google.guava:guava:jar:20.0:compile [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime {code} So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of `drools-core`optaplanner-persistence-xstream`, etc into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO. It would be nice if we could make this a bit more modular. > KIE-Server-Client needs to be more light-weight > ----------------------------------------------- > > Key: DROOLS-1661 > URL: https://issues.jboss.org/browse/DROOLS-1661 > Project: Drools > Issue Type: Enhancement > Components: kie server > Affects Versions: 7.1.0.Beta3 > Reporter: Duncan Doyle > Assignee: Edson Tirelli > > KIE-Server-Client currently drags in a ton of dependencies. A {{mnv dependency:tree}} gives this output: > {code} > +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile > [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile > [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile > [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile > [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile > [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile > [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile > [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile > [INFO] | | +- com.google.guava:guava:jar:20.0:compile > [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile > [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile > [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile > [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile > [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile > [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile > [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile > [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile > [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile > [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile > [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile > [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile > [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile > [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile > [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile > [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile > [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile > [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile > [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile > [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile > [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile > [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile > [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile > [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile > [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile > [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime > {code} > So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of {{drools-core}}, {{optaplanner-persistence-xstream}}, etc into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO. > It would be nice if we could make this a bit more modular. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1661) KIE-Server-Client needs to be more light-weight

by Duncan Doyle (JIRA)

Duncan Doyle created DROOLS-1661: ------------------------------------ Summary: KIE-Server-Client needs to be more light-weight Key: DROOLS-1661 URL: https://issues.jboss.org/browse/DROOLS-1661 Project: Drools Issue Type: Enhancement Components: kie server Affects Versions: 7.1.0.Beta3 Reporter: Duncan Doyle Assignee: Edson Tirelli KIE-Server-Client currently drags in a ton of dependencies. A `mnv dependency:tree` gives this output. ``` +- org.kie.server:kie-server-client:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.apache.commons:commons-lang3:jar:3.4:compile [INFO] | +- org.kie:kie-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.uberfire:uberfire-maven-support:jar:1.1.0-SNAPSHOT:compile [INFO] | +- org.kie:kie-internal:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.optaplanner:optaplanner-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.drools:drools-compiler:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.antlr:antlr-runtime:jar:3.5:compile [INFO] | | | +- org.eclipse.jdt.core.compiler:ecj:jar:4.4.2:compile [INFO] | | | \- com.google.protobuf:protobuf-java:jar:2.6.0:compile [INFO] | | +- org.apache.commons:commons-math3:jar:3.4.1:compile [INFO] | | +- com.google.guava:guava:jar:20.0:compile [INFO] | | +- org.reflections:reflections:jar:0.9.10:compile [INFO] | | | \- com.google.code.findbugs:annotations:jar:2.0.1:compile [INFO] | | \- com.thoughtworks.xstream:xstream:jar:1.4.9:compile [INFO] | | +- xmlpull:xmlpull:jar:1.1.3.1:compile [INFO] | | \- xpp3:xpp3_min:jar:1.1.4c:compile [INFO] | +- org.drools:drools-core:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.mvel:mvel2:jar:2.3.0.Final:compile [INFO] | | \- commons-codec:commons-codec:jar:1.10:compile [INFO] | +- org.kie:kie-dmn-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | \- org.kie:kie-dmn-model:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.kie.server:kie-server-api:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-xstream:jar:7.1.0-SNAPSHOT:compile [INFO] | | | \- org.optaplanner:optaplanner-persistence-common:jar:7.1.0-SNAPSHOT:compile [INFO] | | +- org.optaplanner:optaplanner-persistence-jaxb:jar:7.1.0-SNAPSHOT:compile [INFO] | | | +- org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec:jar:1.0.4.Final:compile [INFO] | | | \- javax.activation:activation:jar:1.1.1:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-annotations:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.6.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.6.2:compile [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.6.2:compile [INFO] | +- org.jboss.spec.javax.ws.rs:jboss-jaxrs-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- org.kie.server:kie-server-common:jar:7.1.0-SNAPSHOT:compile [INFO] | +- org.codehaus.jackson:jackson-xc:jar:1.9.13:compile [INFO] | | \- org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile [INFO] | +- org.codehaus.jackson:jackson-mapper-asl:jar:1.9.13:compile [INFO] | +- org.jboss.spec.javax.jms:jboss-jms-api_2.0_spec:jar:1.0.0.Final:compile [INFO] | +- com.sun.xml.bind:jaxb-core:jar:2.2.11:compile [INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.11:compile [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.7.7:runtime ``` So, if we're just creating a simple DMN KIE-Server Client, we are dragging in all sorts of `drools-core`optaplanner-persistence-xstream`, etc into our project. Obviously we can start excluding theses dependencies, but that's not really that user friendly IMO. It would be nice if we could make this a bit more modular. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7152) Activate CDI request context during concurrency utilities task execution

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/WFLY-7152?page=com.atlassian.jira.plugin.... ] Tomas Remes commented on WFLY-7152: ----------------------------------- Is there any idea how to do this? If I understand it correctly there is the problem how to introduce e.g. {{ManagedExecutorServiceService}} dependency to {{BeanManager}}(Service) because these EE concurrent utilities are shared across deployments AFAIK (or am I wrong?). I have dummy prototype at my [branch|https://github.com/tremes/wildfly/tree/WFLY-7152] but it's using {{CDI.current()}} which is not much reliable. > Activate CDI request context during concurrency utilities task execution > ------------------------------------------------------------------------ > > Key: WFLY-7152 > URL: https://issues.jboss.org/browse/WFLY-7152 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, EE > Reporter: Martin Kouba > Assignee: David Lloyd > > This is not required by any spec (CDI, Concurrency Utilities for Java EE). But it might be useful. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1652) Add an entry point on the kie-server to deploy a DMN files as a service

by Duncan Doyle (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1652?page=com.atlassian.jira.plugi... ] Duncan Doyle commented on DROOLS-1652: -------------------------------------- Valid points Maciej. I think the expectation is that something like this would survive restarts and goes beyond the "5-minute demo". (otherwise I don't really see the point. For a simple demo you can also use BC, import a file manually and press "Build and Deploy"). However, that indeed means that we now need to be able to do "mvn deploy" to the actual Maven repository used by the system (as in: any Maven repo, Our internal one, but als. repo's like Nexus, Artifactory, etc, when running in a production scenario). > Add an entry point on the kie-server to deploy a DMN files as a service > ----------------------------------------------------------------------- > > Key: DROOLS-1652 > URL: https://issues.jboss.org/browse/DROOLS-1652 > Project: Drools > Issue Type: Feature Request > Components: dmn engine, kie server > Affects Versions: 7.1.0.Beta3 > Reporter: Edson Tirelli > Assignee: Duncan Doyle > > Add an end point on the kie-server to deploy a DMN xml file directly as a service without the need for a kjar. > In other words, the end point would accept a POST with a DMN xml file as a payload, it would internally build a kjar in memory and deploy it as a kie-container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1660) Temporal operator fails after serialization

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1660?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1660: -------------------------------- Component/s: core engine > Temporal operator fails after serialization > ------------------------------------------- > > Key: DROOLS-1660 > URL: https://issues.jboss.org/browse/DROOLS-1660 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.0.0.Final > Reporter: Christopher Brecht > Assignee: Edson Tirelli > Attachments: EventA.java, Reproducer.java > > > I attached a reproducer of the problem. If I am executing the rules without serialization everything is working correctly. > If I am executing it with serialization the rules are firing to often. I expect the rule to fire only once. It should fire once at 03:06:00 but it fires 3 times, once at 3:04:00 and 2 times at 3:06:00. > It have to be a problem with serialization of the temporal operators like after,before, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1660) Temporal operator fails after serialization

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1660?page=com.atlassian.jira.plugi... ] Mario Fusco reassigned DROOLS-1660: ----------------------------------- Assignee: Mario Fusco (was: Edson Tirelli) > Temporal operator fails after serialization > ------------------------------------------- > > Key: DROOLS-1660 > URL: https://issues.jboss.org/browse/DROOLS-1660 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.5.0.Final, 7.0.0.Final > Reporter: Christopher Brecht > Assignee: Mario Fusco > Attachments: EventA.java, Reproducer.java > > > I attached a reproducer of the problem. If I am executing the rules without serialization everything is working correctly. > If I am executing it with serialization the rules are firing to often. I expect the rule to fire only once. It should fire once at 03:06:00 but it fires 3 times, once at 3:04:00 and 2 times at 3:06:00. > It have to be a problem with serialization of the temporal operators like after,before, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-139) Targetted refresh - MIQ Sprint-64

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-139?page=com.atlassian.jira.pl... ] Hayk Hovsepyan reassigned HAWKULARQE-139: ----------------------------------------- Assignee: Hayk Hovsepyan (was: Michael Foley) > Targetted refresh - MIQ Sprint-64 > --------------------------------- > > Key: HAWKULARQE-139 > URL: https://issues.jboss.org/browse/HAWKULARQE-139 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Hayk Hovsepyan > > Summary: Enhancement for updating the status of deployments and servers frequently without the need in manual refresh > Slide Deck: Slide-Deck: https://www.slideshare.net/ManageIQ/sprint-64 > PR: https://github.com/ManageIQ/manageiq-providers-hawkular/pull/27 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1660) Temporal operator fails after serialization

by Christopher Brecht (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1660?page=com.atlassian.jira.plugi... ] Christopher Brecht updated DROOLS-1660: --------------------------------------- Stackoverflow ID: 45006239 (was: 6356907) > Temporal operator fails after serialization > ------------------------------------------- > > Key: DROOLS-1660 > URL: https://issues.jboss.org/browse/DROOLS-1660 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final, 7.0.0.Final > Reporter: Christopher Brecht > Assignee: Edson Tirelli > Attachments: EventA.java, Reproducer.java > > > I attached a reproducer of the problem. If I am executing the rules without serialization everything is working correctly. > If I am executing it with serialization the rules are firing to often. I expect the rule to fire only once. It should fire once at 03:06:00 but it fires 3 times, once at 3:04:00 and 2 times at 3:06:00. > It have to be a problem with serialization of the temporal operators like after,before, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1660) Temporal operator fails after serialization

by Christopher Brecht (JIRA)

Christopher Brecht created DROOLS-1660: ------------------------------------------ Summary: Temporal operator fails after serialization Key: DROOLS-1660 URL: https://issues.jboss.org/browse/DROOLS-1660 Project: Drools Issue Type: Bug Affects Versions: 7.0.0.Final, 6.5.0.Final Reporter: Christopher Brecht Assignee: Edson Tirelli Attachments: EventA.java, Reproducer.java I attached a reproducer of the problem. If I am executing the rules without serialization everything is working correctly. If I am executing it with serialization the rules are firing to often. I expect the rule to fire only once. It should fire once at 03:06:00 but it fires 3 times, once at 3:04:00 and 2 times at 3:06:00. It have to be a problem with serialization of the temporal operators like after,before, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 July 2017