Is your feature request related to a problem? Please describe.
I'm migrating a fairly large legacy set of applications to Polylith. I've moved a legacy internal test-helper lib into a component, but it still references namespaceas that do not conform to the top-namespace rule. In the transition phase, which could last of months (maybe years), I'd like to leave the namespaces and their consumers as they are (to avoid non-productive busywork).
As it stands, every invcation of the Poly tool emits warnings like:
Warning 205: Non top namespace logback.xml was found in test-helper, files: components/test-helper/../../central-api-server/resources/logback.xml
Warning 205: Non top namespace oiiku-central-api.http was found in test-helper, files: components/test-helper/../../central-api-server/src/oiiku_central_api/http/handler.clj, components/test-helper/../../central-api-server/src/oiiku_central_api/http/middleware.clj, components/test-helper/../../central-api-server/src/oiiku_central_api/http/routes.clj
There are 19 such warnings, all of them from the test-helper component.
Describe the solution you'd like
I'd like an option disable warning 205 for a component, analogous to the 207 :necessary option for projects.
Describe alternatives you've considered
I guess I could just ignore the warnings, but this has the risk of "warning fatigue": I'd risk not noticing new warnings that actually matter.
Additional context
Clojure 1.12.5, Polylith 0.3.32, polylith-external-test-runner 0.9.1
Is your feature request related to a problem? Please describe.
I'm migrating a fairly large legacy set of applications to Polylith. I've moved a legacy internal test-helper lib into a component, but it still references namespaceas that do not conform to the top-namespace rule. In the transition phase, which could last of months (maybe years), I'd like to leave the namespaces and their consumers as they are (to avoid non-productive busywork).
As it stands, every invcation of the Poly tool emits warnings like:
There are 19 such warnings, all of them from the
test-helpercomponent.Describe the solution you'd like
I'd like an option disable warning 205 for a component, analogous to the 207
:necessaryoption for projects.Describe alternatives you've considered
I guess I could just ignore the warnings, but this has the risk of "warning fatigue": I'd risk not noticing new warnings that actually matter.
Additional context
Clojure 1.12.5, Polylith 0.3.32, polylith-external-test-runner 0.9.1