You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multiple plugins on a project that call Project#afterEvaluate do not play nice with one another. In particular, I received an error message from another plugin about this call that I believe is the result of that plugin being applied after this one (Docker) thanks to task dependencies in a multi-project build. Here is the link to the relevant ticket for the other plugin which includes a pull request where I'm removing the Project#afterEvaluate call for that plugin.
What did you want to happen?
I want all the plugins I use to play together nicely, so I'm on a mission to prompt everyone to eliminate their use of Project#afterEvaluate. The use in this project appears to be a little more involved than in the one I linked here, so it may require a bit of noodling to figure out how to replicate the functionality without using Project#afterEvaluate. I'm happy to help. I'll probably look more into the code soon.
The text was updated successfully, but these errors were encountered:
What happened?
Multiple plugins on a project that call
Project#afterEvaluate
do not play nice with one another. In particular, I received an error message from another plugin about this call that I believe is the result of that plugin being applied after this one (Docker) thanks to task dependencies in a multi-project build. Here is the link to the relevant ticket for the other plugin which includes a pull request where I'm removing theProject#afterEvaluate
call for that plugin.What did you want to happen?
I want all the plugins I use to play together nicely, so I'm on a mission to prompt everyone to eliminate their use of
Project#afterEvaluate
. The use in this project appears to be a little more involved than in the one I linked here, so it may require a bit of noodling to figure out how to replicate the functionality without usingProject#afterEvaluate
. I'm happy to help. I'll probably look more into the code soon.The text was updated successfully, but these errors were encountered: