I can certainly understand your first point that making layout required could
increase the burden of upgrading. I'm not sure I understand why you say
forcing the developer to set the layout would cause Gradle to no longer work
out of the box with existing Gradle-layout repositories. That would only be
true if they set the layout to something other than "gradle". The point is
that by forcing them to set it they are cognizant of the fact that they are
using the non-standard layout which is completely non-obvious today. What
would also help with this is some mention in the documentation. I just sent
a PR to update the docs: https://github.com/gradle/gradle/pull/367
It's an interesting idea to add error messages and reporting, which could be
helpful if you're trying to read from a repository, but I think that
generally works pretty well today. The case where it wouldn't help
unfortunately is with what I think is the worse problem of publishing to a
repository in non-standard format. Maybe we could require the layout be set
only when publishing? I'm not sure if that's possible, but it seems like it
would lessen the burden of forcing developers to update their build scripts
and solve most of the problem I'm worried about.
Another idea would be to force the layout only when the repository url is
"${System.properties['user.home']}/.ivy2/local". You really probably don't
want to be writing to the default ivy repository in a non-default format.
-Ben
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Making-layout-required-for-ivy-repositories-tp5713196p5713198.html
Sent from the gradle-dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
