Ok - I found one answer - not sure if it is the simplest.
compile.getOptions().fork([memoryMaximumSize:"256m"]) One things concerns me here - the fact that there appears to be a direct, explicitly defined mapping between the javac attributes defined by Ant and the options supported by the the java plugin compile task. My concern here is that this means that any new release of Ant will require that all plugins be updated to reflect removed/new attributes. For example, if in Ant 1.7.+ the javac Ant task adds a new attribute will I have to wait for someone to update the plugin to support the new attribute? If this is so, then IMHO gradle has a "heavy wrapper" problem similar to what I saw in Maven 1.0 where it could take months (actually years) between the time of a new Ant release and Maven support of the new features. Is there anyway/would it be a good idea to allow one to attach arbitrary attributes to a Gradle task? -steve -- View this message in context: http://www.nabble.com/compile-task-configuration---set-memoryMaximumSize-tp19765855p19766773.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
