On Feb 11, 2009, at 9:45 AM, Marco Hunsicker wrote:
Hello Hans,
Regarding the naming scheme I was wondering why the archive_jar
task does not use camelcase notation. All other default tasks seem
to use consists naming. Is there a specific reason for the
difference or is this just an oversight? Thanks.
Thanks for pointing this out. There is no deeper reason for the
current naming scheme of archive tasks. In fact we are revisiting
the way we name archive tasks for 0.6.
Thanks for looking into this. I might add that I find the Ant
approach to simply map common tool names to task names pretty
straightforward. It's quite consistent and provides little surprise.
Another observation regarding naming of the Java tasks, is that the
names does not always map to activities. Instead of "compileTests"
which would be a concise description of what the task does, you use
"testCompile". Again no biggie, having read the documentation just
once you will know that this will compile any tests, but
semantically it leaves room from interpretation. Just a thought.
Thanks.
Your proposal makes a lot of sense and I think we should change this.
I have filed a Jira: http://jira.codehaus.org/browse/GRADLE-396
Please don't hesitate to criticize such issues. This is very much
appreciated. The primary focus of our next releases will be to improve
the user experience and naming is an important part of this.
Thanks
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
