I noticed that gradle-core/build.gradle has dependencies declared in multiple
sections. There are 7 different compile declarations and 3 runtime ones. Are
these intended to provide some meaningful grouping of the dependencies that
needs to be maintained or is this something that can be cleaned up? There are
some dependencies (like ant) that are declared multiple times. There are also
dependencies that are in both the runtime and compile configurations. If we try
to maintain groups of dependencies that logically go together, you are bound to
get this type of duplication. I don't know that this is bad, however.
I'll be glad to remove duplicates and create entries in the libraries map for
all these (so the versions can be maintained in one place), but I wasn't sure
what was desired here.
--
Steve Appling
Automated Logic Research Team
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
