[jboss-jira] [JBoss JIRA] (WFLY-5227) Move security-manager subsystem from WildFly to WildFly Core
Brian Stansberry (JIRA)
issues at jboss.org
Tue Nov 29 19:27:05 EST 2016
[ https://issues.jboss.org/browse/WFLY-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13331230#comment-13331230 ]
Brian Stansberry commented on WFLY-5227:
----------------------------------------
Re: the GAV, yeah, it's probably easier to deal with it in on go. Changing it later will involve yet another dance of coordinated changes.
I just looked and the only uses of this artifact are in the servlet-feature-pack, which would go away regardless as the module will instead be packaged up in core's core-feature-pack. So really the only people who might care about this GAV are 1) layered products (highly doubtful) or 2) Swarm (reasonably likely as they slice and dice the server.)
I'll ping [~hbraun] to see if changes this GAV matters to them, and if it does whether maintaining an empty pom with the old GAV is helpful.
> Move security-manager subsystem from WildFly to WildFly Core
> ------------------------------------------------------------
>
> Key: WFLY-5227
> URL: https://issues.jboss.org/browse/WFLY-5227
> Project: WildFly
> Issue Type: Bug
> Components: Security Manager
> Reporter: Josef Cacek
> Assignee: Ken Wills
> Priority: Critical
>
> It's not possible to define security permissions in WildFly Core without {{security-manager}} subsystem. Therefore the subsystem should be moved from WildFly to the Core.
> More details in the [Permissions in WildFly Core|http://lists.jboss.org/pipermail/wildfly-dev/2015-August/thread.html#4353] thread on {{wildfly-dev}} mailing list.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list