[
https://issues.jboss.org/browse/WFCORE-114?page=com.atlassian.jira.plugin...
]
Brian Stansberry updated WFCORE-114:
------------------------------------
Fix Version/s: 1.0.0.CR2
(was: 1.0.0.CR1)
I'm deferring this to CR2, although it may get bumped to 2.0.0.Alpha1. The question is
whether we want to bump the size of core by the ~940Kb of picketbox.
Emmanuel, your PR might be valid anyway, as it allows someone building off core to get
vault support simply by installing the module. Right now they'd have to go to Full to
get vault support.
Elytron may end up being nearly as big as picketbox, so trying to avoid the weight in
1.0.0 may just be delaying the inevitable.
As a tradeoff, we can consider aggressively dropping jboss-common-core, in 1.0, which in
production code is only used by domain-management module for Base64. In 2.0 that will
switch to JDK 8 provided code. For 1.x we could just fork Base64 stuff into
domain-management and drop the 650Kb jboss-common-core.
Get RuntimeVaultReader into WildFly Core
----------------------------------------
Key: WFCORE-114
URL:
https://issues.jboss.org/browse/WFCORE-114
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.0.0.Alpha8
Reporter: Brian Stansberry
Assignee: ehsavoie Hugonnet
Priority: Blocker
Fix For: 1.0.0.CR2
The only real implementation of AbstractVaultReader isn't in wildfly-core; it's
in the wildfly-full security subsystem module.
This means WildFly Core currently doesn't really support vault expressions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)