[JBoss JIRA] (DROOLS-5434) Incorrect warning about file declaring wrong package
by Magnus Larsson (Jira)
[ https://issues.redhat.com/browse/DROOLS-5434?page=com.atlassian.jira.plug... ]
Magnus Larsson commented on DROOLS-5434:
----------------------------------------
[~mfusco] These problems re-appeared and I did some quick testing. I think it should have been the *packageNameFromFolder* = getRelativePackageName( packageNameForFolder);. Attaching an image of debug output below, _packageNameForFile_ is already containing the correct package (read from the .drl file), but _packageNameForFolder_ contains the spring-boot prefix, thus the warning still appears in the log. Sorry for the delayed response, I just found it again by chance.
!image-2020-09-03-09-20-10-089.png!
> Incorrect warning about file declaring wrong package
> ----------------------------------------------------
>
> Key: DROOLS-5434
> URL: https://issues.redhat.com/browse/DROOLS-5434
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Magnus Larsson
> Assignee: Mario Fusco
> Priority: Major
> Attachments: image-2020-09-03-09-20-10-089.png
>
>
> I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not.
> I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls:
> {code:java}
> // packageNameForFile prints warning if package in .drl file is not same as flatted directory structure
> // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning
> String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file );
> // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded
> return isPackageInKieBase( kieBase, pkgNameForFile );
> {code}
> As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded).
> Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (DROOLS-5434) Incorrect warning about file declaring wrong package
by Magnus Larsson (Jira)
[ https://issues.redhat.com/browse/DROOLS-5434?page=com.atlassian.jira.plug... ]
Magnus Larsson updated DROOLS-5434:
-----------------------------------
Attachment: image-2020-09-03-09-20-10-089.png
> Incorrect warning about file declaring wrong package
> ----------------------------------------------------
>
> Key: DROOLS-5434
> URL: https://issues.redhat.com/browse/DROOLS-5434
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Reporter: Magnus Larsson
> Assignee: Mario Fusco
> Priority: Major
> Attachments: image-2020-09-03-09-20-10-089.png
>
>
> I am running Drools in a Spring-Boot jar and get the following warning statement _File 'BOOT-INF/classes/com/example/test/TEST.drl' is in folder 'BOOT-INF/classes/com/example/test' but declares package 'com.example.test'. It is advised to have a correspondance between package and folder names_. The package name in the drl file is correct, the problem is just that _BOOT-INF.classes._ isn't considered when evaluating if printing the warning or not.
> I have tracked it down to *KieBuilderImpl.java*, method *isFileInKieBase*. The last 2 lines in that method calls:
> {code:java}
> // packageNameForFile prints warning if package in .drl file is not same as flatted directory structure
> // Does not care about SUPPORTED_RESOURCES_ROOTS, thus prints the warning
> String pkgNameForFile = packageNameForFile( fileName, folderNameForFile, !useFolders, file );
> // Does care about SUPPORTED_RESOURCES_ROOTS, so the drl file is loaded
> return isPackageInKieBase( kieBase, pkgNameForFile );
> {code}
> As it is implemented right now, the warning might either be a false-positive (and still get loaded), or the package is wrong (and the file is not loaded).
> Voting to include the SUPPORTED_RESOURCES_ROOTS as valid prefixes when checking if the warning should be printed.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-346) Bootable JAR - Second bootable JAR fails to package if first uses certain layers
by Jan Kasik (Jira)
[ https://issues.redhat.com/browse/WFWIP-346?page=com.atlassian.jira.plugin... ]
Jan Kasik updated WFWIP-346:
----------------------------
Description:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
was:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
> Bootable JAR - Second bootable JAR fails to package if first uses certain layers
> --------------------------------------------------------------------------------
>
> Key: WFWIP-346
> URL: https://issues.redhat.com/browse/WFWIP-346
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Jan Kasik
> Assignee: Jean Francois Denise
> Priority: Critical
>
> See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
> If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "rollback-on-runtime-failure" => true,
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("interface" => "public")],
> [ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.weld")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.naming")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.ee")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
> [ERROR] }
> [ERROR] ]
> [ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
> {noformat}
> Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3 -pl app-two}} ends with success. Same for {{app-one}} only.
> If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-346) Bootable JAR - Second bootable JAR fails to package if first uses certain layers
by Jan Kasik (Jira)
[ https://issues.redhat.com/browse/WFWIP-346?page=com.atlassian.jira.plugin... ]
Jan Kasik updated WFWIP-346:
----------------------------
Description:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
was:
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules builds successfully.
> Bootable JAR - Second bootable JAR fails to package if first uses certain layers
> --------------------------------------------------------------------------------
>
> Key: WFWIP-346
> URL: https://issues.redhat.com/browse/WFWIP-346
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Jan Kasik
> Assignee: Jean Francois Denise
> Priority: Critical
>
> See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
> If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "rollback-on-runtime-failure" => true,
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("interface" => "public")],
> [ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.weld")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.naming")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.ee")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
> [ERROR] }
> [ERROR] ]
> [ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
> {noformat}
> Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
> If I replace layers in app-one with layer {{cloud-server}} both modules build successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-346) Bootable JAR - Second bootable JAR fails to package if first uses certain layers
by Fabio Burzigotti (Jira)
[ https://issues.redhat.com/browse/WFWIP-346?page=com.atlassian.jira.plugin... ]
Fabio Burzigotti updated WFWIP-346:
-----------------------------------
Summary: Bootable JAR - Second bootable JAR fails to package if first uses certain layers (was: Second bootable JAR fails to package if first uses certain layers)
> Bootable JAR - Second bootable JAR fails to package if first uses certain layers
> --------------------------------------------------------------------------------
>
> Key: WFWIP-346
> URL: https://issues.redhat.com/browse/WFWIP-346
> Project: WildFly WIP
> Issue Type: Bug
> Reporter: Jan Kasik
> Assignee: Jean Francois Denise
> Priority: Critical
>
> See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
> If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "rollback-on-runtime-failure" => true,
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("interface" => "public")],
> [ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.weld")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.naming")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.ee")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
> [ERROR] },
> [ERROR] {
> [ERROR] "operation" => "add",
> [ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
> [ERROR] }
> [ERROR] ]
> [ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
> {noformat}
> Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
> If I replace layers in app-one with layer {{cloud-server}} both modules builds successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFWIP-346) Second bootable JAR fails to package if first uses certain layers
by Jan Kasik (Jira)
Jan Kasik created WFWIP-346:
-------------------------------
Summary: Second bootable JAR fails to package if first uses certain layers
Key: WFWIP-346
URL: https://issues.redhat.com/browse/WFWIP-346
Project: WildFly WIP
Issue Type: Bug
Reporter: Jan Kasik
Assignee: Jean Francois Denise
See the reproducer: https://github.com/honza-kasik/layer-conflict - there are two Maven modules, each configured to run WildFly Maven JAR plugin.
If I run {{mvn clean package -Dversion.org.wildfly.jar.plugin=2.0.0.Beta3}}, bootable JAR for app-one builds but for app-two the build ends up with an error and app-two fails to package:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-jar-maven-plugin:2.0.0.Beta3:package (default) on project app-two: Provisioning failed: Failed to generate standalone.xml on {
[ERROR] "operation" => "composite",
[ERROR] "address" => [],
[ERROR] "rollback-on-runtime-failure" => true,
[ERROR] "steps" => [
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("interface" => "public")],
[ERROR] "inet-address" => "${jboss.bind.address:127.0.0.1}"
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.bean-validation")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.weld")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.naming")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.ee")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.io")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.wildfly.extension.undertow")]
[ERROR] },
[ERROR] {
[ERROR] "operation" => "add",
[ERROR] "address" => [("extension" => "org.jboss.as.jaxrs")]
[ERROR] }
[ERROR] ]
[ERROR] }: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-8" => "WFLYCTL0310: Extension module org.jboss.as.jaxrs not found"}}
{noformat}
Packaging when running {{mvn clean install -Dversion.org.wildfly.jar.plugin=2.0.0.Beta2 -pl app-two}} ends with success. Same for {{app-one}} only.
If I replace layers in app-one with layer {{cloud-server}} both modules builds successfully.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (DROOLS-5617) Refacto MiningModel source generation
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-5617:
----------------------------------------
Summary: Refacto MiningModel source generation
Key: DROOLS-5617
URL: https://issues.redhat.com/browse/DROOLS-5617
Project: Drools
Issue Type: Task
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
For code generation, currently, all sources of segment models of a MiningModel are put in the main (container) model sourcemap, and the list of "nested models" is empty.
Scope of this refactor is to populate the list of nested models with the "HasSourcesMap" version of all the models, and populate the "main" sourcemap only with the MiningModel specific sources
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (DROOLS-5616) Be able to set with an Env Variable that KIE using XStream does not complain on unknown fields
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5616?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi moved RHDM-1446 to DROOLS-5616:
-------------------------------------------------
Project: Drools (was: Red Hat Decision Manager)
Key: DROOLS-5616 (was: RHDM-1446)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: kie server
(was: Kie-Server)
Environment: (was: In our project "Migration Analytics" we have our integration (camel) app sending requests to the KIE Server. Everything deployed on Openshift.
Sometimes the integration app evolves adding new fields to the pojos being sent to KIE, but now we need to wait for the changes done on the project deployed in KIE to be able to merge the first PR on the integration.
I know XStream has a method called ".ignoreUnknownElements()" so the proposal would be to have an environment variable that KIE would read and execute that method just after creating the unmarshaller.)
QE Status: NEW
> Be able to set with an Env Variable that KIE using XStream does not complain on unknown fields
> ----------------------------------------------------------------------------------------------
>
> Key: DROOLS-5616
> URL: https://issues.redhat.com/browse/DROOLS-5616
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13821) Add a Galleon layer for the distributable web subsystem configured with a local web cache
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-13821:
---------------------------------------
Summary: Add a Galleon layer for the distributable web subsystem configured with a local web cache
Key: WFLY-13821
URL: https://issues.redhat.com/browse/WFLY-13821
Project: WildFly
Issue Type: Feature Request
Components: Clustering, Web (Undertow)
Reporter: Brian Stansberry
Assignee: Yeray Borges Santana
Fix For: 21.0.0.Beta1
We have a web-clustering layer that provides the distributable-web subsystem and the related infinispan web session caching resources, configured for multi-server distributed sessions.
We need a variant of this with infinispan configured for local caching.
The WFLY-13099 standalone-microprofile.xml config should have this kind of setup; otherwise session sharing does not work . (A failure in org.jboss.as.test.clustering.cluster.web.shared.SharedSessionTestCase if the server uses a config without it shows this.) For WFLY-13099 I can work around this by adding the needed config stuff without a layer, but as everything else needed for those configs are from layers, it's better to use a layer in WF 20.
Besides it's a good layer to have anyway. :)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months