>> We definitely have and will have much shorter release cycles. Shorter release cycles will help, but really can't be guaranteed especially as complexity grows, and the number of plugins - especially thirdparty - supplied grow in number, complexity and usage.
>> If definitely would make sense to be able to assign arbitrary >> attributes for the forked JVM and the call to javac. In general I'm >> not sure. The feature you are proposing would simply create a >> namespace for each task, right? I hadn't really given much thought to implementation, but a namespace would be one way. The problem that I see now is to do what I suggested requires some iffy assumptions and/or detailed knowledge of the plugin internals. I made the assumption that compile was essentially a call to the ant javac task. In that context my request made sense. Under a different implementation - like direct calls to javac - my request makes no sense and would be dangerous. One thing I hated about Maven was the complexity of the plugins and the rigidity in behavior (not to mention bugs). It wasn't unusual to lose confidence in a plugin and start seriously considering writing one's own - which negated a lot of the value of Maven. It would be nice if Gradle avoided that "feature" <grin> Thanks! -steve -- View this message in context: http://www.nabble.com/compile-task-configuration---set-memoryMaximumSize-tp19765855p19768179.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
