Hide Forgot
Wrong information in EAP6 integration testsuite RBAC pom.xml. artifactId and name should follow other integration module patterns. artifactId: Currently: 'wildfly-ts-integ-rbac' Recommended: 'jboss-as-integ-rbac' name: Currently: 'WildFly Test Suite: Integration - Role Based Access Control' Recommended: 'JBoss Application Server Test Suite: Integration - Role Based Access Control'
WildFly is the upstream project for EAP. Its name is no more invalid than jboss-as or "JBoss Application Server", neither of which are the official name of the product. There is going to be more and more appearance of "WildFly" in EAP sources as code from upstream is backported. It's impossible to keep it out and IMHO it is a waste of time to try. EAP 7 will actually start from WildFly code so for sure there isn't going to be some attempt to scrub this kind of thing from the entire source code.
Scrubbing it from the source would be unnecessary overkill, so the name probably isn't important since it's just a description thing, but the actual project structure, artifactId, should follow established patterns. If we want EAP7 to follow Wildfly project structure that's fine. I'm always for fewer unnecessary changes and maintenance. If we want to even convert EAP6 to Wildfly structure to make backporting easier I'm all for it. If we mix Wildfly and EAP6 project structure though... I'm not for that at all. Project structure should follow the pattern. wildfly-ts-integ-rbac means I can't find that project where I expect it to be, given the other 9 testsuite project artifactIds. One project shouldn't randomly break the naming pattern that way. Neither is 'right', technically speaking, but breaking structure patterns is still wrong.
I don't much care if this module gets renamed, so long as the practice doesn't spread.
As far as I (QA) am concerned, I don't really care either. And it's a test suite component, so customer impact is probably negligible.