October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2839) Document how to run Drools with a flat classpath by merging kie.conf files

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-2839?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2839: -------------------------------- Fix Version/s: 7.13.0.Final > Document how to run Drools with a flat classpath by merging kie.conf files > -------------------------------------------------------------------------- > > Key: DROOLS-2839 > URL: https://issues.jboss.org/browse/DROOLS-2839 > Project: Drools > Issue Type: Task > Components: docs > Affects Versions: 7.9.0.Final > Reporter: Duncan Doyle > Assignee: Mario Fusco > Priority: Major > Fix For: 7.13.0.Final > > > When running Drools in a Fat JAR, for example created by the Maven Shade Plugin, the various "kie.conf" files of the Drools JARs (e.g. drools-core, drools-compiler) need to be merged, otherwise , the Fat JAR will contain only 1 kie.conf from a single dependency, resulting into errors. > This is for example required when running Drools in a Vert.x application. > You can merge resources in the Maven Shade Plugin using transformers, like this: > {code} > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > {code} > For example, in my Vert.x app this is the full config of the Maven Shade Plugin: > {code} > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-shade-plugin</artifactId> > <version>3.1.0</version> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>shade</goal> > </goals> > <configuration> > <transformers> > <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"> > <manifestEntries> > <Main-Class>io.vertx.core.Launcher</Main-Class> > <Main-Verticle>${main.verticle}</Main-Verticle> > </manifestEntries> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/services/io.vertx.core.spi.VerticleFactory</resource> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > </transformers> > <artifactSet> > </artifactSet> > <outputFile>${project.build.directory}/${project.artifactId}-${project.version}-fat.jar</outputFile> > </configuration> > </execution> > </executions> > </plugin> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2839) Document how to run Drools with a flat classpath by merging kie.conf files

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-2839?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2839: -------------------------------- Sprint: 2018 Week 39-41 (was: 2018 Week 42-44) > Document how to run Drools with a flat classpath by merging kie.conf files > -------------------------------------------------------------------------- > > Key: DROOLS-2839 > URL: https://issues.jboss.org/browse/DROOLS-2839 > Project: Drools > Issue Type: Task > Components: docs > Affects Versions: 7.9.0.Final > Reporter: Duncan Doyle > Assignee: Mario Fusco > Priority: Major > > When running Drools in a Fat JAR, for example created by the Maven Shade Plugin, the various "kie.conf" files of the Drools JARs (e.g. drools-core, drools-compiler) need to be merged, otherwise , the Fat JAR will contain only 1 kie.conf from a single dependency, resulting into errors. > This is for example required when running Drools in a Vert.x application. > You can merge resources in the Maven Shade Plugin using transformers, like this: > {code} > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > {code} > For example, in my Vert.x app this is the full config of the Maven Shade Plugin: > {code} > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-shade-plugin</artifactId> > <version>3.1.0</version> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>shade</goal> > </goals> > <configuration> > <transformers> > <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"> > <manifestEntries> > <Main-Class>io.vertx.core.Launcher</Main-Class> > <Main-Verticle>${main.verticle}</Main-Verticle> > </manifestEntries> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/services/io.vertx.core.spi.VerticleFactory</resource> > </transformer> > <transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"> > <resource>META-INF/kie.conf</resource> > </transformer> > </transformers> > <artifactSet> > </artifactSet> > <outputFile>${project.build.directory}/${project.artifactId}-${project.version}-fat.jar</outputFile> > </configuration> > </execution> > </executions> > </plugin> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11165) Eliminate unessential module dependencies on the org.jboss.as.transactions module

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11165: --------------------------------------- Summary: Eliminate unessential module dependencies on the org.jboss.as.transactions module Key: WFLY-11165 URL: https://issues.jboss.org/browse/WFLY-11165 Project: WildFly Issue Type: Enhancement Components: Class Loading, Management, Transactions Reporter: Brian Stansberry Assignee: Brian Stansberry As part of our work on getting maximum benefit from Galleon, we want to eliminate unnecessary hard dependencies between Galleon packages, most of which are just provisioning wrappers around the FS content for our JBoss Modules modules. So that means cutting dependency links between modules. The org.jboss.as.transactions module necessarily has a large dependency tree, so if other modules depend on it, they then also have a large dependency tree, perhaps much larger than whatever they really need. So I want to eliminate such dependencies whereever possible. There are quite a few modules that depend on org.jboss.as.transactions solely for ServiceName constants for services that provide value types not from org.jboss.as.transactions, e.g. TransactionManager which is from the javax.transaction.api module. So the main (perhaps only) task here will be to eliminate those links. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4115) JDK11 - GC logging format needs to be reviewed

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4115?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4115: --------------------------------------- I honestly have never looked at JDK 8 GC logs and barely JDK 11 logs now :) I think we need someone from GSS to give a review as they are the ones that use these the most. [~bmaxwell] is there someone that can look at this? There's likely nothing we can do and just using the Java 11 tools instead of Java 8 tools should likely work. > JDK11 - GC logging format needs to be reviewed > ---------------------------------------------- > > Key: WFCORE-4115 > URL: https://issues.jboss.org/browse/WFCORE-4115 > Project: WildFly Core > Issue Type: Bug > Components: Scripts, Server > Reporter: Marek Kopecký > Assignee: James Perkins > Priority: Major > Labels: Java11, jdk11 > > * Weird naming of gc log files > ** I test this with JDK11 > ** I start standalone and stop standalone > ** JDK10 creates JBOSS_HOME/standalone/log/gc.log (with detailed information) and JBOSS_HOME/standalone/log/gc.log.0 (with brief summary of gc logging) > ** I start standalone and stop standalone again > ** JDK10 moves original gc.log to gc.log.1 > ** JDK10 keep original gc.log.0 > ** JDK10 creates new gc.log (with detailed information) and gc.log.2 (with brief summary of gc logging) > ** Can this be changed by GC settings? > * GC logs are much more verbose against jdk8 gc logs. Can this be fixed by some JDK10 gc settings? > This is follow up for WFCORE-3996 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11113) Update to JAXB 2.3.1

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-11113?page=com.atlassian.jira.plugin... ] Alessio Soldano commented on WFLY-11113: ---------------------------------------- [~jamezp], no, I think we do not want to split this upgrade from the jbws and resteasy one, otherwise you would have quite a mess with imports and exclusions of different jaxb versions... > Update to JAXB 2.3.1 > -------------------- > > Key: WFLY-11113 > URL: https://issues.jboss.org/browse/WFLY-11113 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Affects Versions: 14.0.0.Final > Reporter: Jan Blizňák > Assignee: Alessio Soldano > Priority: Major > Labels: Java11 > Fix For: 15.0.0.Alpha1 > > > The new release of JAXB should fix some issues with JDK11 (such as warnings WFLY-11044) > Full diff https://github.com/javaee/jaxb-v2/compare/2.3.0...2.3.1 > Note: this release no longer contains jaxb-core artifact which was merged into jaxb-runtime https://github.com/javaee/jaxb-v2/commit/32fda2fbee71c2df04c52fc8eb368769... > Note2: there is a change in dependencies, some of the org.glassfish.jaxb:* artifacts used to depend on relaxngDatatype:relaxngDatatype (which is excluded in WF \[1\],\[2\],\[3\]), now replaced with com.sun.xml.bind.external:relaxng-datatype. WF is using com.github.relaxng:relaxngDatatype instead, not sure, if it is compatible out of the box. > \[1\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L1293-L1298 > \[2\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L3848-L3853 > \[3\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L6728 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11164) Upgrade RESTEasy to 3.6.1.SP1

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-11164: -------------------------------------- Summary: Upgrade RESTEasy to 3.6.1.SP1 Key: WFLY-11164 URL: https://issues.jboss.org/browse/WFLY-11164 Project: WildFly Issue Type: Component Upgrade Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 15.0.0.Alpha1 Upgrade RESTEasy to 3.6.1.Final for better JDK11 compatibility. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11163) Upgrade JBossWS to 5.2.4.Final

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-11163: -------------------------------------- Summary: Upgrade JBossWS to 5.2.4.Final Key: WFLY-11163 URL: https://issues.jboss.org/browse/WFLY-11163 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 15.0.0.Alpha1 Upgrade JBossWS to 5.2.4.Final (including all sub-components), for better JDK11 compatibilty. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11152) Upgrade JBossWS to 5.2.4.Final

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-11152?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-11152: ----------------------------------- Description: Upgrade JBossWS to 5.2.4.Final (including all sub-components), for better JDK11 compatibilty. (was: Upgrade JBossWS to 5.2.4.Final (including all sub-components), for better JDK11 compatibilty. This also includes upgrade Apache CXF to 3.2.6 version.) > Upgrade JBossWS to 5.2.4.Final > ------------------------------ > > Key: WFLY-11152 > URL: https://issues.jboss.org/browse/WFLY-11152 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 15.0.0.Alpha1 > > > Upgrade JBossWS to 5.2.4.Final (including all sub-components), for better JDK11 compatibilty. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11162) The DsMgmtTestBase abstract test shouldn't use the DataSourceSubsystemParser from the extension

by James Perkins (Jira)

James Perkins created WFLY-11162: ------------------------------------ Summary: The DsMgmtTestBase abstract test shouldn't use the DataSourceSubsystemParser from the extension Key: WFLY-11162 URL: https://issues.jboss.org/browse/WFLY-11162 Project: WildFly Issue Type: Bug Components: JCA, Test Suite Reporter: James Perkins Assignee: Stefano Maestri The {{DataSourceSubsystemParser}} abstract test has a {{marshalAndReparseDsResources(String)}} method which uses the {{DataSourceSubsystemParser}} from the connector extension. Tests that do XML configuration parsing should be part of the unit tests not the integration tests. In this case it's a smoke test in the integration test suite. Once done the {{org.wildfly:wildfly-connector}} should be removed as a dependency from the smoke tests. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11161) Update to JAXB 2.3.1

by Alessio Soldano (Jira)

Alessio Soldano created WFLY-11161: -------------------------------------- Summary: Update to JAXB 2.3.1 Key: WFLY-11161 URL: https://issues.jboss.org/browse/WFLY-11161 Project: WildFly Issue Type: Component Upgrade Components: REST, Web Services Affects Versions: 14.0.0.Final Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 15.0.0.Alpha1 The new release of JAXB should fix some issues with JDK11 (such as warnings WFLY-11044) Full diff https://github.com/javaee/jaxb-v2/compare/2.3.0...2.3.1 Note: this release no longer contains jaxb-core artifact which was merged into jaxb-runtime https://github.com/javaee/jaxb-v2/commit/32fda2fbee71c2df04c52fc8eb368769... Note2: there is a change in dependencies, some of the org.glassfish.jaxb:* artifacts used to depend on relaxngDatatype:relaxngDatatype (which is excluded in WF \[1\],\[2\],\[3\]), now replaced with com.sun.xml.bind.external:relaxng-datatype. WF is using com.github.relaxng:relaxngDatatype instead, not sure, if it is compatible out of the box. \[1\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L1293-L1298 \[2\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L3848-L3853 \[3\] https://github.com/wildfly/wildfly/blob/master/pom.xml#L6728 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 2018