sdedic commented on PR #4517: URL: https://github.com/apache/netbeans/pull/4517#issuecomment-1221889908
> > ```java > GradleJavaProject gjp = GradlJavaProject.get(project); > File jar = gjp.getMainJar(); > ``` Well, the main issue is not to find exactly the jar; but - what the `build` actually does. Different plugins glue different tasks to `build` lifecycle one. For this, I've analyzed the inter-Task dependencies. It can be still approximated from just known Plugins though. - what the `native-image` output is - in the case native buld. Not just the jar. The idea to separate the loading process seems good, as it duplicates the infrastructure. I would initially (since I need some results soon) drop the task _properties_ introspection (assuming separate APIs for loading the data) - as actually the task proeprties default to (combination of) proiject extension values, it's a good approximation and a good tradeoff for me. Are you sure we're not instantiating Tasks even with the current implementation ;) ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@netbeans.apache.org For additional commands, e-mail: notifications-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
