Help with unresolved file paths during plugin execution for banDuplicateClasses
I posted this as an issue on the Github project before I realized the mailing list was more appropriate and was more active for this. Apologies for the double post.
The Github issue is here along with a link to the demo project that illustrates the issue:https://github.com/mojohaus/extra-enforcer-rules/issues/29
It appears that there is a bug when using the banDuplicateClasses rule where the file path for the dependency that is being checked hasn't been resolved during the plugin execution.
Thanks for advance for any pointers on how I can proceed to resolve this. I spent time attempting to debug it, and what I believe I found was that the list of dependencyArtifacts that is handed to the plugin has the artifact flagged as resolved even though the file attribute hasn't been populated.