It is probably too late in the game for these types of questions, but
here goes anyway. :)
Gradle is working out really well for me, but I have one small gripe.
I use bash autocomplete a lot. I also do a lot of "cd build" or "vi
build.gradle" or "vi buildSrc/xyz". The gripe is that all of these
start with "build" and so the autocompletion beeps for each of them. I
presume the build and build.gradle names are to be similar to ant,
maven uses pom.xml and target. I am not sure I have any better
suggestions for them, maybe "build" could be "gradleOut" or
"output.gradle" ? To be really old school and borrow from make,
"build.gradle" could be "gradlefile". :)
I assume that buildSrc is treated differently than src because it is
more like a subproject than a regular source directory, but I wonder
if buildSrc could be renamed to src/build? That would have the
advantage of keeping all source files in one directory.
I know all these are configurable, but I really think there is great
advantage to sticking to the convention for these types of things.
Probably bash could be configured to know the difference as well,
haven't had time to try that.
As I said, it is probably too late and this is probably not a
sufficient reason to rethink the file/directory naming convention, so
just tossing this out.
thanks,
Philip
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
