As for the PS bit. Perhaps a config option in the settings or build file at the top level that specifies the debuging options but is only used when an optional "-Ddebug.test" or "-Ddebug.source" option is specified. And perhaps an option in the ~/.gradle that overrides that.
Cheers Matt --- On Fri, 6/2/09, Matthew Fudge <[email protected]> wrote: > From: Matthew Fudge <[email protected]> > Subject: [gradle-user] Short cut during build > To: [email protected] > Date: Friday, 6 February, 2009, 7:05 PM > 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. > > 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. > > Cheers > > Matt > > > > > --------------------------------------------------------------------- > 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
