Hi Hans,
> What is your top list of missing features?
That is a good question. I haven't really thought about this.
Unfortunately JIRA is down, so I can't check issues right now. But I
remember some things:
- update BND version - AFAIK Gradle uses some archaic version of
bnd, thus the bundles it creates are not perfect
- make it possible for Gradle to do what other tools can, e.g.:
- execute single tests
- provide archetypes (to easily start projects using gradle)
- provide easy way to integrate with other libraries (Cobertura, Aspectj)
- make things that help people convert from other tools (e.g. there
was a ticket regarding XSLT transormation of pom.xml to print
dependencies in Gradle's format)
I think Gradle is quite mature, and offers a lot of super
functionality. What it lacks IMHO is a short way to achieve results. I
mean, not everyone will be willing to read the userguide. I expect
many people to just google for "Gradle Selenium" or "use Gradle with
AspecJ" and leave disappointed because there is no easy 3-lines code
snippet that they can use "just like that". That's why I'd put a lot
of effort into explaining how to do typical stuff with Gradle (yeah,
the cookbook is the place I'd love to see such explanations).
BTW. Sometimes on the mailing list you can find emails - especially
written by you and Adam (but also others) - that explains brilliantly
what are the features of Gradle and where its strength lies. For
example the recent one titled "Using modules to separate JDK
dependencies". I wonder if such things can be somehow included into
the userguide... They are worth "publishing", that is for sure !
--
Tomek
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
