On 11 June 2014 at 3:33:35 am, Peter Ledbrook (pe...@cacoethes.co.uk) wrote:
> The issue with #1 is that users of the new version will have to change their > apply(plugin: «id») statements to use the new qualified id. I prefer this approach as long as it's combined with appropriate feedback. Mentioning this in the release notes is important, but would it be possible to add a check when the build is executed? I'm thinking along the lines of, if no qualified ID is present in the apply() statement, then: 1. warn that the user may have to update the ID We could do this. The need to change will only occur when the user updates the plugin version, so the new qualified id will be on the classpath. 2. check whether the plugin repository contains a plugin of the same name, but with a qualified ID and let the user know that such is available. I don’t think this is worth it. As said above, this only comes about when users upgrade the plugin and the plugin changed to a qualified ID. So we can assume that in most cases the qualified ID is on the classpath and just do #1. Peter -- Peter Ledbrook t: @pledbrook --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email — Luke Daley Gradleware Join us for Gradle Summit 2014, June 12th and 13th in Santa Clara, CA: http://www.gradlesummit.com
