[
https://issues.apache.org/jira/browse/NETBEANS-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055795#comment-17055795
]
Anthony Vanelverdinghe commented on NETBEANS-3188:
--------------------------------------------------
[~skygo] another strategy would be to migrate all code (where possible) to use
an external Maven installation (i.e. use the Maven CLI instead of the Java
API). This migration can be done gradually, and eventually it would become
relatively easy to upgrade the bundled installation, or even stop bundling
Maven completely. Yet another strategy would be to bundle 2 Maven installations
and gradually migrate from the obsolete to the new version, but I'm not sure
how feasible that is. (Note that this is very similar to how NetBeans uses an
embedded JGit instead of the native Git installation, i.e. NETBEANS-2122)
Imho this issue is important because the bundled Maven installation is used
even for basic operations such as merely opening a Maven project, which results
in issues such as NETBEANS-2499
> Upgrade bundled Maven
> ----------------------
>
> Key: NETBEANS-3188
> URL: https://issues.apache.org/jira/browse/NETBEANS-3188
> Project: NetBeans
> Issue Type: Bug
> Affects Versions: 11.1, 11.2
> Reporter: Geertjan Wielenga
> Priority: Major
> Fix For: 11.3
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
