Hi Alex, I'm the developer of the NetBeans integration of Gradle and pleased to hear that you want to work on this part of the Tooling API.
May I be selfish enough to ask you to consider my needs as well? :) I have already reported two RFE for improving the model loading: 1. http://forums.gradle.org/gradle/topics/tooling_api_fetch_multiple_models_in_a_single_method_call 2. http://forums.gradle.org/gradle/topics/tooling_api_let_us_know_if_multiple_projects_got_evaluated I will summarize those two RFEs: 1. Allow loading multiple models in a single call (similar as you have recommended) but also allow to define "fall-back models". That is return another model if the one requested is not available. There is no use for this currently but could make things easier if a model is to be made obsolete (replaced by other models). 2. Evaluating a Gradle project will likely cause other Gradle projects to be evaluated as well. So, instead of leting evaluated projects go to waste. Let the client code request what other projects got evaluated and allow retrieving models from those projects as well. This is advantageous if you do not wish to load all the projects of a multi-project build and should work well with the configuration on deman feature of Gradle (when/if it will be implemented for model loading as well). Although these things are not vital (although advantageous) for simple J2SE projects. These changes would improve performance considerably when NBAndroid plugin is installed as well. Currently, installing NBAndroid will slow down the loading of each project by magnitudes, simply because I have to determine for each subproject if it has an AndroidProject as well. Thanks again for taking your time on improving the Tooling API. bye, Attila Kelemen -- View this message in context: http://gradle.1045684.n5.nabble.com/Proposal-for-retrieving-multiple-types-of-models-from-a-project-in-a-single-pass-using-the-Tooling-AI-tp5711516p5711534.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
