[jboss-jira] [JBoss JIRA] (WFLY-10335) Elytron testsuite resource should be in java directory

[Stuart Douglas (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572009#comment-13572009 ] 

Stuart Douglas commented on WFLY-10335:
---------------------------------------

So to elaborate a bit the main reason behind this is that WildFly is different to a lot  applications that are build using maven. If you are building a standard application you have one copy of each relevant descriptor, if you have special test version of them it is fine to have them in src/test/resources, as they are used for all tests. 

WildFly is not like this, every test has its own deployment descriptors. There is simply no point in having a mirrored package structure, it just means that you need to look at multiple locations to fully understand a test, and generally complicates the code base. In general we will follow maven conventions unless there is a good reason not to, and in this case the benefit of having all test resources being self contained is a lot more important that following the maven conventions.

> Elytron testsuite resource should be in java directory
> ------------------------------------------------------
>
>                 Key: WFLY-10335
>                 URL: https://issues.jboss.org/browse/WFLY-10335
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Test Suite
>    Affects Versions: 12.0.0.Final
>            Reporter: Jan Kalina
>            Assignee: Jan Kalina
>            Priority: Minor
>
> As request by [~swd847], elytron testsuite (wildfly/testsuite/integration/elytron) should have resources in src/test/java directory, instead of src/test/resources, to be consistent with the rest of the testsuites.
> ??they are in src/test/resources rather than src/test/java like the rest of the test suite??
> ??If you look back maybe 6-7 years there was a discussion on wildly dev as to why we do it this way??



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)