On Sep 18, 2009, at 10:18 PM, Adam Murdoch wrote:
Hans Dockter wrote:
On Sep 18, 2009, at 11:07 AM, Russel Winder wrote:
On Fri, 2009-09-18 at 11:00 +0200, Hans Dockter wrote:
On Sep 18, 2009, at 10:29 AM, Russel Winder wrote:
On Fri, 2009-09-18 at 10:19 +0200, Hans Dockter wrote:
- We don't litter .gradle dirs through the source tree. I find
this
quite annoying, and I don't imagine I'm alone.
Minor point to support this. I really enjoy that GitHub is not
polluting every source dir like svn does. I can easily copy stuff
around.
This is a Git, Bazaar, Mercurial feature, not a GitHub feature.
Even I know this ;). Sorry for the typo.
No problem, I'm just making sure everyone's awake ;-)
Real irritation of the moment is that versions of dependencies of
Gradle
are now getting scattered around the place, some required but . . .
Also many of the version of dependencies used in Gradle are now
really
very old.
Which ones do you have in mind?
Should there be a programme of moving to latest versions of
everything. And should this be a continuous activity or something
done
once a week, once a month, once a quarter, once a year, once a
decade, . . .
It should be a continued manual activity rather at the beginning of
a new release stream.
I have created a Wiki page for this:
http://docs.codehaus.org/display/GRADLE/Libs+Gradle+Core
We could potentially automate this - it would make an interesting
addition to the project reports.
We should provide a description property for a dependency. That way we
could have really a nice automated report.
In creating the list for the wiki I have realized again how important
it is to be able to express first-level and transitive dependencies,
as we can't do this in our build at the moment because of the module
bug. That way is was a real pain.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
