[
https://issues.jboss.org/browse/WFLY-11171?page=com.atlassian.jira.plugin...
]
James Perkins commented on WFLY-11171:
--------------------------------------
[~dlofthouse] If we have the
{{org.wildfly.extension.batch.jberet.deployment.BatchPermission}} extend the new
permission, say {{org.jberet.BatchPermission}}, will using the old permission name still
work? I'm not sure how inheritance with permissions work.
Test in Elytron integration tests rely on the BatchPermission in
wildfly-jberet
-------------------------------------------------------------------------------
Key: WFLY-11171
URL:
https://issues.jboss.org/browse/WFLY-11171
Project: WildFly
Issue Type: Bug
Components: Batch, Test Suite
Reporter: James Perkins
Assignee: Cheng Fang
Priority: Major
Tests in the Elytron integration test suite rely on
{{org.wildfly.extension.batch.jberet.deployment.BatchPermission}} which is in private
module. This permission should likely be moved to a public JBeret API or a new public API
should be create within WildFly that exposes this permission. There is a chance this
permission may be required for users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)