Closed codeconsole closed 11 months ago
@puneetbehl Can you at least make it an option to run excludeDependencies?
You can default it to run, but give the end user the ability to not have the exclusion added to every dependency.
Perhaps a simple fix would be to ONLY have this exclusion rule added IF the plugin java-library
is not being used.
Or again, at least have a plugin option to not force the addition of the rule.
I am not sure exactly why the rule is there, but the only viable reason I can see is if it is mean to help the end user.
If a library is being built, the exclusions can be added to the specific dependencies that actually have a transitive slf4j-simple
library
However, I really think this rule can just be removed. If it is that important, it should just be added to the grails-app create-app
generated build.gradle
file. But even then, I think it is poor design to have a global exclusion for a hypothetical scenario. Perhaps you can explain why the rule was added?
Here is an example of how the exclusion should be handled on individual dependencies and not have a global exclude enforced by the plugin.
The following code
results in really nasty plugin poms.
if you create a Grails plugin, that exclude gets added to EVERY dependency (including dependences that don't even have slf4j!):
For example, look at this mess:
@puneetbehl Is there another way of going about this? There should not be a global exclusion like this.
An exclusion:
should only exist when library is actually dependent on
slf4j-simple
.