To set some background resources for our test classes in maven are in a folder that matches the name of the unit test.
e.g for a class com.myco.myprod.sytem.foo.bar.WhizzTest the resources would be in src/test/resources/com/myco/myprod/system/foo/bar/WhizzTest/
So far so good.
But using m2e when the resources folder is added due to the inclusion/exclusion filter you donât get the nice âpackageâ list under the resources â instead you get a tree structure.
Due to the tree structure (if you use a mouse) you need to drill down many layers to see what resources are in that folder â or to get to a specific resource.
I am well aware of the reason to have the filter (as without it you will end up with un maven-filtered resources in the output folder) â but I have a cunning plan and was wondering if there was any drawbacks â and if it could be implemented in a pseudo lifecycle binding or if this is something that could only be done in the core (if so if it was made optional would it be something that would be accepted into m2e)?
The cunning plan is to change the includes and excludes
and then for each directory in the resources folder create the .dummyFile.
optionally this file can then be manually excluded from source control.