You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Svatopluk Dedic (Jira)" <ji...@apache.org> on 2021/04/13 09:44:00 UTC

[jira] [Resolved] (NETBEANS-5482) Support for explicit parameters for the application and its VM

     [ https://issues.apache.org/jira/browse/NETBEANS-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Svatopluk Dedic resolved NETBEANS-5482.
---------------------------------------
    Resolution: Fixed

> Support for explicit parameters for the application and its VM
> --------------------------------------------------------------
>
>                 Key: NETBEANS-5482
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-5482
>             Project: NetBeans
>          Issue Type: Improvement
>          Components: projects - Gradle
>    Affects Versions: 12.3
>            Reporter: Svatopluk Dedic
>            Assignee: Svatopluk Dedic
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 12.4
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> In NetBeans *12.3*, a way how a caller can launch the user application, passing application parameters and launcher (VM) parameters in an abstract way was introduced. Maven implementation was done as a proof of concept.
> In order to better support Micronaut development, I need to do the same for Micronaut-based applications, which mostly use gradle build - Micronaut itself is built by gradle, so it's natural to cover both Micronaut-supported build systems with the feature.
> During analysis, I have noticed that Gradle Java support does not honour *StartupExtender* API, which is used by other NB plugins to inject VM-level parameters; so this task should also cover implementing that support for better integration of Gradle Java with the rest of NetBeans IDE.
> The general idea is:
>  * mix in JVM arguments provided by {{StartupExtender}}s. 
>  * define a project property, interpreted by NetBeans Tooling plugin, since Gradle itself does not accept commandline arg or project property that would affect the JVM settings
>  * implement a token replacer, that would generate necessary commandline items for gradle build, that will be interpreted directly by Gradle, or the Plugin
>  * Change the default {{action-mapping.xml}} to use those new tokens, for javaExec related actions.
>  * Update documentation to instruct users how to change *existing* action-mappings
> Eventually some migration tool may be provided, but documentation should be enough, our users are _developers_, after all.
> The above should ensure, that for newly opened projects, the implemented support will work 'out of the box'. Existing projects may need to be upgraded - in the IDE-related part.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists