July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGTOOL-127) Allow expression properties to be resolved from system properties and environment variables

by James Perkins (JIRA)

James Perkins created LOGTOOL-127: ------------------------------------- Summary: Allow expression properties to be resolved from system properties and environment variables Key: LOGTOOL-127 URL: https://issues.jboss.org/browse/LOGTOOL-127 Project: Log Tool Issue Type: Enhancement Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 2.1.0.Alpha3 Currently some annotations allow for expressions to be defined for certain attributes. These values are resolved from a properties file passed as an annotation processor argument. It may be useful for system properties for environment variables to be resolved. For system properties the expression prefix would be {{sys}}: {code} ${sys.key} {code} For environment variables the expression prefix would be {{env}}: {code} ${env.key} {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2204) Deprecate DONT_BUNDLE message flag

by Bela Ban (JIRA)

Bela Ban created JGRP-2204: ------------------------------ Summary: Deprecate DONT_BUNDLE message flag Key: JGRP-2204 URL: https://issues.jboss.org/browse/JGRP-2204 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Although {{Message$Flag.DONT_BUNDLE}} is ignored by the transports, it is still a valid message flag. Deprecate this flag and remove all uses of it by JGroups itself. Can't remove it until the next major version, as this would break client code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2204) Deprecate DONT_BUNDLE message flag

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2204?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2204: --------------------------- Fix Version/s: 4.0.5 > Deprecate DONT_BUNDLE message flag > ---------------------------------- > > Key: JGRP-2204 > URL: https://issues.jboss.org/browse/JGRP-2204 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.5 > > > Although {{Message$Flag.DONT_BUNDLE}} is ignored by the transports, it is still a valid message flag. > Deprecate this flag and remove all uses of it by JGroups itself. Can't remove it until the next major version, as this would break client code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9092) Access jndi datasource outside eap container?

by harit kumar (JIRA)

harit kumar created WFLY-9092: --------------------------------- Summary: Access jndi datasource outside eap container? Key: WFLY-9092 URL: https://issues.jboss.org/browse/WFLY-9092 Project: WildFly Issue Type: Feature Request Components: EE Reporter: harit kumar Access jndi datasource outside eap container? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9091) "Arguments must not be null" when sending a null JSON object with ResteasyWebTarget

by Romain Pelisse (JIRA)

[ https://issues.jboss.org/browse/WFLY-9091?page=com.atlassian.jira.plugin.... ] Romain Pelisse reassigned WFLY-9091: ------------------------------------ Assignee: Romain Pelisse (was: Alessio Soldano) > "Arguments must not be null" when sending a null JSON object with ResteasyWebTarget > ----------------------------------------------------------------------------------- > > Key: WFLY-9091 > URL: https://issues.jboss.org/browse/WFLY-9091 > Project: WildFly > Issue Type: Bug > Components: REST > Reporter: Romain Pelisse > Assignee: Romain Pelisse > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9091) "Arguments must not be null" when sending a null JSON object with ResteasyWebTarget

by Romain Pelisse (JIRA)

Romain Pelisse created WFLY-9091: ------------------------------------ Summary: "Arguments must not be null" when sending a null JSON object with ResteasyWebTarget Key: WFLY-9091 URL: https://issues.jboss.org/browse/WFLY-9091 Project: WildFly Issue Type: Bug Components: REST Reporter: Romain Pelisse Assignee: Alessio Soldano -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (AG-26) document where the public build artifacts live for the open source community

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-26?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-26. ----------------------------- Resolution: Done It's documented on the official site: http://agroal.github.io/releases.html Added a mention in the project's README as well. > document where the public build artifacts live for the open source community > ---------------------------------------------------------------------------- > > Key: AG-26 > URL: https://issues.jboss.org/browse/AG-26 > Project: Agroal > Issue Type: Enhancement > Components: web > Affects Versions: 0.2 > Reporter: Paulo Lopes > Assignee: Luis Barreiro > > I'm trying to get agroal integrated with vertx jdbc client upsteam and for that we need a way to get the official build artifacts, preferably from maven central. I can't seem to find them and I didn't noticed where I could find them when quickly looking at the website. > Without this I can't submit the Pull Request I have to make agroal a option for connection pool at vert.x side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

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

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1661?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1661: --------------------------------------- Geoffrey, Is there a way to make these dependencies optional? so if the user is using the kie-server-client only for rules/process/solver he only needs the respective dependencies instead of everything? > 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: Maciej Swiderski > > 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)

9 years

1
0
0 / 0

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

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1661?page=com.atlassian.jira.plugi... ] Edson Tirelli edited comment on DROOLS-1661 at 7/17/17 8:44 AM: ---------------------------------------------------------------- [~ge0ffrey] Is there a way to make these dependencies optional? so if the user is using the kie-server-client only for rules/process/solver he only needs the respective dependencies instead of everything? was (Author: tirelli): Geoffrey, Is there a way to make these dependencies optional? so if the user is using the kie-server-client only for rules/process/solver he only needs the respective dependencies instead of everything? > 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: Maciej Swiderski > > 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)

9 years

1
0
0 / 0

[JBoss JIRA] (AG-26) document where the public build artifacts live for the open source community

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-26?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro updated AG-26: ---------------------------- Component/s: web > document where the public build artifacts live for the open source community > ---------------------------------------------------------------------------- > > Key: AG-26 > URL: https://issues.jboss.org/browse/AG-26 > Project: Agroal > Issue Type: Enhancement > Components: web > Affects Versions: 0.2 > Reporter: Paulo Lopes > Assignee: Luis Barreiro > > I'm trying to get agroal integrated with vertx jdbc client upsteam and for that we need a way to get the official build artifacts, preferably from maven central. I can't seem to find them and I didn't noticed where I could find them when quickly looking at the website. > Without this I can't submit the Pull Request I have to make agroal a option for connection pool at vert.x side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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