just raised one http://jira.codehaus.org/browse/GRADLE-388
Cheers Matt --- On Fri, 6/2/09, Adam Murdoch <[email protected]> wrote: > From: Adam Murdoch <[email protected]> > Subject: Re: [gradle-user] Short cut during build > To: [email protected] > Date: Friday, 6 February, 2009, 8:00 PM > Matthew Fudge wrote: > > Hi all, > > > > I there any way to persude a subproject of gradle not > to compile its dependencies? I'm working on a fairly > large system and once I've built it it would be nice to > move on to the next subproject and try to fix that up in the > knowledge that its dependencies have not changed so there is > no need to compile them and run thier tests again. A command > line option perhaps to say "I know your dependencies > have them selves not changed to don't build them > again" just use their pre built classpath. > > > > > > There's nothing yet. We want to solve this problem > soon, hopefully in > the Gradle 0.6 or 0.7 release. > > > As I said the conversion to gradle I am working on is > fairly large and it is taking longer and longer to do the > conversion as I bring new subprojects into the gradle build. > > > > It may also be useful for debugging test cases > rapidly. > > > > PS is there any way of telling a subproject of gradle > to run in debug mode so that you can drop into a debugger > just for the code or tests in that module (I hacked around > and turned off forking for tests and added the debug string > to GRADLE_OPTS but this is quite inconvinient. > > > > > > This is a good idea. Can you add a JIRA issue for it? > > > Adam > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
