Is there any way to actively test if a maven dependency scope is set to “test” but would be required to be “compile”/“runtime”? I broke a build that way but can’t think of any way to catch that.
@jakesmolka Was thinking about https://maven.apache.org/enforcer/enforcer-rules/index.html, but unfortunatly no (ouless you write your own rules using BeanShell - not a bad language per se, but just one more java dialect)