On Apr 11, 2009, at 10:14 AM, Russel Winder wrote:
Hans,
On Sat, 2009-04-11 at 07:55 +0200, Hans Dockter wrote:
[ . . . ]
Yes, 0.6 will have breaking changes.
I have no problem with that, Gradle is still in development towards
1.0.
I think though that there needs to be strong support for bleeding edge
users (aka early adopters). In particular I think there probably
needs
to be a webpage detailing all the principal 0.5 -> 0.6 changes (or
maybe
this already exists), updated as the changes get committed to trunk.
This helps those people who are super early adopters and use trunk for
production use deal with the changes as they happen.
In particular, a recent commit has brought this change to the DSL --
and
that is fine, this is trunk. I just think it wise to make the changes
more public and announced for all the super-early adopters (who are
actually your alpha testers and so are worthy of support :-)
I agree. We need such a Wiki page in any case (at the latest when we
release). Sometimes it is hard though as some committed
implementations are also a live proposal for further discussion and
still likely to change.
I have set up such a page (with no content yet):
http://docs.codehaus.org/display/GRADLE/Gradle+0.6+breaking+changes
- Hans
you have to refactor the addMavenRepo out of the dependencies into:
repositories {
mavenCentral()
}
There are now additional samples in the samples directory. Have a
look
for example at the java/quickstart example.
OK, I will update my Gradle files to the new syntax and report back.
--
Russel.
============================================================
Dr Russel Winder Partner
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip:
sip:[email protected]
London SW11 1EN, UK. m: +44 7770 465 077 xmpp: [email protected]
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
