Remove duplicate resources from test suite#338
Conversation
28ec3a8 to
6ce95d7
Compare
|
I think I'm seeing some weird issue when applying this patch. It feels like resources are not picked up. |
I know what happened. There are cases we intentionally use a resource named exactly the same as that in production, in order to override. Since |
Another solution would be to set |
Yeah that was what I suggested, and yes the trade-off is duplicating resources in each every test jar. |
|
Totally forgot about this. I think this is still valid, right? |
|
Ooph, I too forgot about this, it should still be valid, looks like I need to resolve a conflict tho, let me get to that |
|
@brian-mcnamara, could you please rebase on |
|
Merged in the latest, will check back on the CI. No worries on the delay, frankly I too forgot about this 🙈 |
|
Looks like everything is healthy. |
|
Shall we merge this? |
See https://github.com/bazel-contrib/rules_jvm/pull/303/files/d899e276ff1a4a9b98272ed6cd31991f09d7839a#r2042301337 for discussion. This change removes library_attrs from the two "classpath healper" libraries (which were introduced as a classpath simplification for bazel), as well as poping the resources from the kwargs if the resources library will include them.
Also added a test case for this