[JBoss JIRA] (DROOLS-5266) Investigate unused dependencies related to Imports screen
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5266?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5266:
--------------------------------
Description:
During work on DROOLS-5262 an unused compile dependencies were reported by {{mvn dependency:analyze}}
h3. kie-wb-config-resource-widget
- org.uberfire:uberfire-commons:jar:7.37.0-SNAPSHOT:compile
- org.kie.soup:kie-soup-project-datamodel-commons:jar:7.37.0-SNAPSHOT:compile
- org.kie.workbench.services:kie-wb-common-services-api:jar:7.37.0-SNAPSHOT:compile
h3. kie-wb-common-library-client
- org.kie.workbench.widgets:kie-wb-config-resource-widget:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-security-api:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-client-all:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-widgets-core-client:jar:7.37.0-SNAPSHOT:compile
- org.kie.workbench.screens:kie-wb-common-library-spaces-screen:jar:7.37.0-SNAPSHOT:compile
was:
During work on DROOLS-5264 an unused compile dependencies were reported by {{mvn dependency:analyze}}
- org.jboss.errai:errai-bus:jar:4.6.0.Final:compile
- org.uberfire:uberfire-commons:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-preferences-client:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-preferences-ui-client:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-client:jar:7.37.0-SNAPSHOT:compile
> Investigate unused dependencies related to Imports screen
> ---------------------------------------------------------
>
> Key: DROOLS-5266
> URL: https://issues.redhat.com/browse/DROOLS-5266
> Project: Drools
> Issue Type: Task
> Affects Versions: 7.37.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> During work on DROOLS-5262 an unused compile dependencies were reported by {{mvn dependency:analyze}}
> h3. kie-wb-config-resource-widget
> - org.uberfire:uberfire-commons:jar:7.37.0-SNAPSHOT:compile
> - org.kie.soup:kie-soup-project-datamodel-commons:jar:7.37.0-SNAPSHOT:compile
> - org.kie.workbench.services:kie-wb-common-services-api:jar:7.37.0-SNAPSHOT:compile
> h3. kie-wb-common-library-client
> - org.kie.workbench.widgets:kie-wb-config-resource-widget:jar:7.37.0-SNAPSHOT:compile
> - org.uberfire:uberfire-security-api:jar:7.37.0-SNAPSHOT:compile
> - org.uberfire:uberfire-client-all:jar:7.37.0-SNAPSHOT:compile
> - org.uberfire:uberfire-widgets-core-client:jar:7.37.0-SNAPSHOT:compile
> - org.kie.workbench.screens:kie-wb-common-library-spaces-screen:jar:7.37.0-SNAPSHOT:compile
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5266) Investigate unused dependencies related to Imports screen
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5266:
-----------------------------------
Summary: Investigate unused dependencies related to Imports screen
Key: DROOLS-5266
URL: https://issues.redhat.com/browse/DROOLS-5266
Project: Drools
Issue Type: Task
Affects Versions: 7.37.0.Final
Reporter: Jozef Marko
Assignee: Jozef Marko
During work on DROOLS-5264 an unused compile dependencies were reported by {{mvn dependency:analyze}}
- org.jboss.errai:errai-bus:jar:4.6.0.Final:compile
- org.uberfire:uberfire-commons:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-preferences-client:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-preferences-ui-client:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-client:jar:7.37.0-SNAPSHOT:compile
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13375) JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters
by Ilia Vassilev (Jira)
[ https://issues.redhat.com/browse/WFLY-13375?page=com.atlassian.jira.plugi... ]
Ilia Vassilev updated WFLY-13375:
---------------------------------
Labels: downstream_dependency (was: )
> JNDI view does not show implementation classes for connection factories and destinations registered by 3rd party resource adapters
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13375
> URL: https://issues.redhat.com/browse/WFLY-13375
> Project: WildFly
> Issue Type: Bug
> Components: Naming
> Reporter: Parul Sharma
> Assignee: Parul Sharma
> Priority: Major
> Labels: downstream_dependency
> Fix For: 20.0.0.Beta1
>
> Attachments: standalone-full.xml, wmq.jmsra.rar
>
>
> If connection factory or JMS destination is configured for third party resource adapter (like IBMMQ 8/9, AMQ 6) then the {{value}} for registered implementation class is {{?}} - see:
> {code}
> [standalone@localhost:9990 /] /subsystem=naming:jndi-view
> {
> "outcome" => "success",
> "result" => {
> "java: contexts" => {
> "java:" => {
> ...
> },
> "jms" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "CF" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> },
> "NmvtisSendQ" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> },
> "topic" => {
> "class-name" => "javax.naming.Context",
> "children" => {
> "T1RHEL6X86_64DYNAMICLARGEOPENJDK18" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> },
> "T2RHEL6X86_64DYNAMICLARGEOPENJDK18" => {
> "class-name" => "java.lang.Object",
> "value" => "?"
> }
> }
> }
> {code}
> There should be provided valid {{value}}, for example {{com.ibm.mq.connector.outbound.ManagedConnectionFactoryImpl}} for "CF" connection factory for IBMMQ.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5265) Investigate unused dependencies of uberfire-m2repo-editor-client
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5265?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5265:
--------------------------------
Sprint: 2020 Week 16-18 (from Apr 13)
> Investigate unused dependencies of uberfire-m2repo-editor-client
> ----------------------------------------------------------------
>
> Key: DROOLS-5265
> URL: https://issues.redhat.com/browse/DROOLS-5265
> Project: Drools
> Issue Type: Task
> Affects Versions: 7.37.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Major
> Labels: drools-tools
>
> During work on DROOLS-5264 an unused compile dependencies were reported by {{mvn dependency:analyze}}
> - org.jboss.errai:errai-bus:jar:4.6.0.Final:compile
> - org.uberfire:uberfire-commons:jar:7.37.0-SNAPSHOT:compile
> - org.uberfire:uberfire-preferences-client:jar:7.37.0-SNAPSHOT:compile
> - org.uberfire:uberfire-preferences-ui-client:jar:7.37.0-SNAPSHOT:compile
> - org.uberfire:uberfire-client:jar:7.37.0-SNAPSHOT:compile
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5265) Investigate unused dependencies of uberfire-m2repo-editor-client
by Jozef Marko (Jira)
Jozef Marko created DROOLS-5265:
-----------------------------------
Summary: Investigate unused dependencies of uberfire-m2repo-editor-client
Key: DROOLS-5265
URL: https://issues.redhat.com/browse/DROOLS-5265
Project: Drools
Issue Type: Task
Affects Versions: 7.37.0.Final
Reporter: Jozef Marko
Assignee: Jozef Marko
During work on DROOLS-5264 an unused compile dependencies were reported by {{mvn dependency:analyze}}
- org.jboss.errai:errai-bus:jar:4.6.0.Final:compile
- org.uberfire:uberfire-commons:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-preferences-client:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-preferences-ui-client:jar:7.37.0-SNAPSHOT:compile
- org.uberfire:uberfire-client:jar:7.37.0-SNAPSHOT:compile
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JGRP-2471) Parse version from POM
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2471?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2471:
---------------------------
Description:
Currently, the version is set in the POM (maven), but also in {{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
With the introduction of maven {{release-plugin}}, modifying the file is manual work that's unwanted.
Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from the POM.
was:
Currently, the version is set in the POM (maven), but also in {{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
With the introduction of maven release-plugin, modifying the file is manual work that's unwanted.
Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from the POM.
> Parse version from POM
> ----------------------
>
> Key: JGRP-2471
> URL: https://issues.redhat.com/browse/JGRP-2471
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0.0.Alpha6
>
>
> Currently, the version is set in the POM (maven), but also in {{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
> With the introduction of maven {{release-plugin}}, modifying the file is manual work that's unwanted.
> Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from the POM.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JGRP-2471) Parse version from POM
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2471?page=com.atlassian.jira.plugin... ]
Bela Ban resolved JGRP-2471.
----------------------------
Resolution: Done
> Parse version from POM
> ----------------------
>
> Key: JGRP-2471
> URL: https://issues.redhat.com/browse/JGRP-2471
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0.0.Alpha6
>
>
> Currently, the version is set in the POM (maven), but also in {{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
> With the introduction of maven {{release-plugin}}, modifying the file is manual work that's unwanted.
> Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from the POM.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JGRP-2470) JBDC_PING can face a split-brain issue when restarting a cooridnator node
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/JGRP-2470?page=com.atlassian.jira.plugin... ]
Radoslav Husar reassigned JGRP-2470:
------------------------------------
Assignee: Radoslav Husar (was: Bela Ban)
> JBDC_PING can face a split-brain issue when restarting a cooridnator node
> -------------------------------------------------------------------------
>
> Key: JGRP-2470
> URL: https://issues.redhat.com/browse/JGRP-2470
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.1.9, 4.0.22
> Reporter: Masafumi Miura
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 4.2.4
>
>
> After [the change|https://github.com/belaban/JGroups/commit/215cdb6] for JGRP-2199, JDBC_PING deletes all entries from the table during the shutdown of the coordinator node.
> This behavior has a possibility to cause a split-brain when restarting a coordinator node. Because, as all entries are lost in the following scenario, the restarting node can not find any information about existing nodes from the table and does not form a cluster.
> 0. node1 and node2 form a cluster. The node1 is a coordinator.
> 1. Trigger a restart of the node1
> 2. The node1 removes their node information from the table
> 3. The node2 becomes a new coordinator
> 4. The node2 updates their node information in the table
> 5. The node1 clears all entries from the table
> 6. The node1 starts again
> 7. The node1 does not join the existing cluster because there's no node information in the table
> Note: If step 5 happens before step 4, the split-brain issue does not happen. However, as step 4 and step 5 happen on different nodes, these steps can happen in parallel. So, the order is undefined. So, for example, if the shutdown of node1 takes a long time, there's a high possibility to face this issue.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years