[JBoss JIRA] (WFCORE-4406) Core Galleon feature-pack pom.xml should define deps as provided
by Jean Francois Denise (Jira)
Jean Francois Denise created WFCORE-4406:
--------------------------------------------
Summary: Core Galleon feature-pack pom.xml should define deps as provided
Key: WFCORE-4406
URL: https://issues.jboss.org/browse/WFCORE-4406
Project: WildFly Core
Issue Type: Enhancement
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
When referencing WildFly core FP as a maven dependency all the dependencies are pulled by maven although they are not required. By making them "provided", the dependencies versions are retrieved when building core feature-pack but dependencies are not downloaded when referencing WildFly core feature-pack.
NB: This implies an upgrade to Galleon 4 for the Galleon plugin to properly retrieve the dependencies versions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-11955) Full and servlet Galleon feature-packs pom.xml should define deps as provided
by Jean Francois Denise (Jira)
Jean Francois Denise created WFLY-11955:
-------------------------------------------
Summary: Full and servlet Galleon feature-packs pom.xml should define deps as provided
Key: WFLY-11955
URL: https://issues.jboss.org/browse/WFLY-11955
Project: WildFly
Issue Type: Enhancement
Components: Build System
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
When referencing a WildFly FP as a maven dependency all the dependencies are pulled by maven although they are not required. By making them "provided", the dependencies versions are retrieved when building Full and Servlet feature-packs but dependencies are not downloaded when referencing WildFly feature-packs.
NB: This implies an upgrade to Galleon 4 for the Galleon plugin to properly retrieve the dependencies versions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-1855) list in guided decision table
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1855?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-1855.
-------------------------------
Resolution: Cannot Reproduce
Comma can be used using brl condition column and template key.
> list in guided decision table
> -----------------------------
>
> Key: DROOLS-1855
> URL: https://issues.jboss.org/browse/DROOLS-1855
> Project: Drools
> Issue Type: Feature Request
> Components: Guided Decision Table Editor
> Affects Versions: 7.3.0.Final
> Reporter: Vijay Yadav
> Assignee: Michael Anstis
> Priority: Major
> Attachments: Screenshot from 2019-04-08 14-33-47.png, Screenshot from 2019-04-08 14-34-21.png, Screenshot from 2019-04-08 14-34-27.png
>
>
> if there is condition in guided decision table( add a condition BRL fragment and use template key), then I am not able to put comma seperated list in corresponding column. it won't allow me to type comma in it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-1855) list in guided decision table
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-1855?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-1855:
--------------------------------
Attachment: Screenshot from 2019-04-08 14-34-27.png
Screenshot from 2019-04-08 14-34-21.png
Screenshot from 2019-04-08 14-33-47.png
> list in guided decision table
> -----------------------------
>
> Key: DROOLS-1855
> URL: https://issues.jboss.org/browse/DROOLS-1855
> Project: Drools
> Issue Type: Feature Request
> Components: Guided Decision Table Editor
> Affects Versions: 7.3.0.Final
> Reporter: Vijay Yadav
> Assignee: Michael Anstis
> Priority: Major
> Attachments: Screenshot from 2019-04-08 14-33-47.png, Screenshot from 2019-04-08 14-34-21.png, Screenshot from 2019-04-08 14-34-27.png
>
>
> if there is condition in guided decision table( add a condition BRL fragment and use template key), then I am not able to put comma seperated list in corresponding column. it won't allow me to type comma in it.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4325) Unable to run testsuite/domain tests with -Delytron
by Ondrej Kotek (Jira)
[ https://issues.jboss.org/browse/WFCORE-4325?page=com.atlassian.jira.plugi... ]
Ondrej Kotek updated WFCORE-4325:
---------------------------------
Description:
Running the {{testsuite/domain}} tests in Elytron mode results in error:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.2.1.Final:execute-commands (default) on project wildfly-core-testsuite-domain: Failed to execute commands: See /home/okotek/test/asts-core-intermit/testsuite/domain/target/wildfly-plugin.log for full details of failure.
[ERROR] Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0122: Server base directory does not exist: /home/okotek/test/asts-core-intermit/testsuite/domain/target/wildfly-core/standalone
{noformat}
WFCORE-4304 excluded {{standalone}} configs that are configured for the Elytron mode by default (see {{testsuite/shared/enable-elytron.cli}}).
The fix for this should be splitting testsuite/shared/enable-elytron.cli into separate scripts for standalone and domain and only executing the appropriate script in the different testsuites.
was:
Running the {{testsuite/domain}} tests in Elytron mode results in error:
{noformat}
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.2.1.Final:execute-commands (default) on project wildfly-core-testsuite-domain: Failed to execute commands: See /home/okotek/test/asts-core-intermit/testsuite/domain/target/wildfly-plugin.log for full details of failure.
[ERROR] Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0122: Server base directory does not exist: /home/okotek/test/asts-core-intermit/testsuite/domain/target/wildfly-core/standalone
{noformat}
WFCORE-4304 excluded {{standalone}} configs that are configured for the Elytron mode by default (see {{testsuite/shared/enable-elytron.cli}}).
> Unable to run testsuite/domain tests with -Delytron
> ---------------------------------------------------
>
> Key: WFCORE-4325
> URL: https://issues.jboss.org/browse/WFCORE-4325
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 8.0.0.CR1
> Reporter: Ondrej Kotek
> Assignee: Ondrej Kotek
> Priority: Major
>
> Running the {{testsuite/domain}} tests in Elytron mode results in error:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.2.1.Final:execute-commands (default) on project wildfly-core-testsuite-domain: Failed to execute commands: See /home/okotek/test/asts-core-intermit/testsuite/domain/target/wildfly-plugin.log for full details of failure.
> [ERROR] Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYSRV0122: Server base directory does not exist: /home/okotek/test/asts-core-intermit/testsuite/domain/target/wildfly-core/standalone
> {noformat}
> WFCORE-4304 excluded {{standalone}} configs that are configured for the Elytron mode by default (see {{testsuite/shared/enable-elytron.cli}}).
> The fix for this should be splitting testsuite/shared/enable-elytron.cli into separate scripts for standalone and domain and only executing the appropriate script in the different testsuites.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month