[JBoss JIRA] (WFCORE-3857) Upgrade to WildFly Galleon plugins 1.0.0.CR6
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created WFCORE-3857:
-----------------------------------------
Summary: Upgrade to WildFly Galleon plugins 1.0.0.CR6
Key: WFCORE-3857
URL: https://issues.jboss.org/browse/WFCORE-3857
Project: WildFly Core
Issue Type: Component Upgrade
Components: Build System
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
This upgrade contains support for colon as a separator between module name and slot in module.xml module dependencies. It still supports the legacy way of specifying the slot using an attribute.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-1649) RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1649?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1649:
-------------------------------------
Fix Version/s: 5.0.0.Beta4
(was: 5.0.0.Beta3)
> RBAC constraint config modifications will fail in a mixed domain if the modified constraint is not present in the legacy slave
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1649
> URL: https://issues.jboss.org/browse/WFCORE-1649
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Critical
> Labels: domain-mode
> Fix For: 5.0.0.Beta4
>
>
> The management model for RBAC constraints is maintained using synthetic resources, with resources only existing for those items (SensitivityClassification and ApplicationClassification) that are registered in the current process. Operations that touch classifications unknown to that process will fail due to missing resource problems.
> This is a big problem in the following scenarios:
> 1) Mixed domain, where legacy slaves do not know about newly introduced classifications.
> 2) Slimming scenarios where slaves are ignoring unrelated parts of the domain wide config and also don't have some extension installed, resulting in classifications registered by those extensions not being present.
> A partial workaround to 1) is for the kernel to register transformers for newly introduced classifications (e.g. SERVER_SSL added in EAP 6.4.7 and EAP 7). But:
> -- that doesn't help with problem 2)
> -- only the kernel can register kernel transformers, so if extensions add new classifications there is no way for them to register the transformer.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3806) Eliminate code that was using transitive MSC dependencies
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3806?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3806:
-------------------------------------
Fix Version/s: 5.0.0.Beta4
(was: 5.0.0.Beta3)
> Eliminate code that was using transitive MSC dependencies
> ---------------------------------------------------------
>
> Key: WFCORE-3806
> URL: https://issues.jboss.org/browse/WFCORE-3806
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Server
> Reporter: Richard Opalka
> Assignee: Richard Opalka
> Fix For: 5.0.0.Beta4
>
>
> Prior MSC 1.2.8 stability monitors were reporting problems if
> some transitive dependency wasn't available. This has changed
> since MSC 1.2.8. There is no notion of transitive
> dependencies in JBoss MSC anymore. If stability monitor detects
> a problem it is always immediate dependency of monitored controller.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-10374) Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR6
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-10374?page=com.atlassian.jira.plugin... ]
Alexey Loubyansky updated WFLY-10374:
-------------------------------------
Description:
1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closing a file writer.
1.0.0.CR6 adds support for colon being a module name/slot separator in module.xml files.
was:1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closing a file writer.
> Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR6
> --------------------------------------------------
>
> Key: WFLY-10374
> URL: https://issues.jboss.org/browse/WFLY-10374
> Project: WildFly
> Issue Type: Component Upgrade
> Components: Build System
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
>
> 1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closing a file writer.
> 1.0.0.CR6 adds support for colon being a module name/slot separator in module.xml files.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3855) Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR6
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3855?page=com.atlassian.jira.plugi... ]
Alexey Loubyansky updated WFCORE-3855:
--------------------------------------
Description:
1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closed file writer.
1.0.0.CR6 adds support for colon being a module name/slot separator in module.xml files.
was:1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closed file writer.
> Upgrade to Galleon 1.0.0.CR3 and plugins 1.0.0.CR6
> --------------------------------------------------
>
> Key: WFCORE-3855
> URL: https://issues.jboss.org/browse/WFCORE-3855
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Build System
> Reporter: Alexey Loubyansky
> Assignee: Alexey Loubyansky
> Fix For: 5.0.0.Beta3
>
>
> 1.0.0.CR3 fixes a file descriptor leak as a consequence of not properly closed file writer.
> 1.0.0.CR6 adds support for colon being a module name/slot separator in module.xml files.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months