Hey,

I was reading through the documentation today and I found the following
text which absolutely makes good sense!

" project does not necessarily represent a thing to be built. It might
represent a thing to be done, such as deploying your application to staging
or production environments. Don't worry if this seems a little vague for
now. Gradle's build-by-convention support adds a more concrete definition
for what a project is.

Each project is made up of one or more *tasks*. A task represents some
atomic piece of work which a build performs. This might be compiling some
classes, creating a JAR, generating javadoc, or publishing some archives to
a repository."


how about renaming build.gradle as the standard filename looking for to
something better ?

like project.gradle?

it could of course fallback on build.gradle to don't brake compability.

otherwise it screams build and that only.


thoughts?


Tomas

Reply via email to