-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publishing plugin? #13
Comments
I just use it to get the publish life-cycle tasks. But thinking about it, it kinda makes sense to check if a |
As far as I remember there is a |
Yeah the problems can arise when the publish plugin gets added after this plugin then. I would need to check how the gradle team creates the tasks. As far as I know they use a new |
If you don't want the publish lifecycle task, but only attach your task to it if it is applied (before or after) you could do it with reactive coding like |
One could also imagine that a Gradle plugin can add a repository type for the publishing plugin, so that the full facilities of the publishing plugin are used and not just the lifecycle tasks. :-) |
Yeah I did this in my other plugin https://github.com/wooga/atlas-paket. I tried with this plugin to have a as much gradle-lishous experience as possible without moving the whole world to get it to work :) The gradle guys don't make it easy sometimes. |
Complain to them, so they can make it easier. :-) |
May I ask why you apply the publishing plugin in your plugin?
Its facilities are nowhere used, are they?
The text was updated successfully, but these errors were encountered: