hdockter wrote: > > > On May 9, 2008, at 9:57 AM, Bert van Brakel wrote: > >> If I currently have a project in maven (1 or 2) and I want to >> switch to >> using gradle, are there any tools for this? >> >> It would be great if gradle just looks for a pom.xml and simply >> runs a maven >> like build. It would certainly help to convince maven users to > > Such functionality is not implemented yet but we plan to this very > soon. Similar to what you have proposed we want to offer 2 things: > > It is an interesting use case we haven't thought of to use Gradle to > add functionality on an existing and still in use Maven build. For > simple Maven builds I see no problem, if the poms use inheritance and > are part of a multiproject build things look more complicated. > > We want to provide this functionality for 0.2. > great, sounds good!
However I think supplementing a current maven build may be a good way to get traction in the enterprise where folks tend to be risk adverse (fair enough), don't have time to rip everything up and start again (after all, time is money and you need to convince alot of people first of the benefits), and developers don't tend to have a lot of time to try out new tools and spend the time to set them up. If out of the box maven support exists then it's a matter of install tool, run, done. The risk and ramp up time is nil, if it doesn't work, then fall back to maven. -- View this message in context: http://www.nabble.com/Out-of-the-box-maven-support--tp17143114p17225951.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
