On 5/1/20 12:23 AM, Geertjan Wielenga wrote:
Well, the user might not have the latest Maven installed. At least we
know for sure that they have the embedded version.
Why can't Netbeans download and use the newest Maven on-the-fly?
Gj
On Fri, 1 May 2020 at 01:38, Ty Young <youngty1...@gmail.com
<mailto:youngty1...@gmail.com>> wrote:
On 4/30/20 6:08 PM, John Mc wrote:
Unless I'm mistaken, NetBeans uses the embedded NetBeans version,
which for NetBeans 12.0 should have Maven 3.6.3 embedded.
There will be another beta version of 12.0 out soon I believe, so
maybe confirm this with that version?
What I'm suggesting is to always use the latest version, not just
the embedded version. Is there any harm in doing so?
Regards
John
On Thu, 30 Apr 2020 at 20:16, Ty Young <youngty1...@gmail.com
<mailto:youngty1...@gmail.com>> wrote:
JIRA: https://issues.apache.org/jira/browse/NETBEANS-4285
Netbeans should, assuming there are no blockers, always use
the latest
Maven release for newly generated projects.
Can this be done? The only issue, IIRC, is that Maven and
JUnit don't
work correctly... but that affects older versions anyway too.
No one
would be forced to upgrade either, it just affects new
projects created
via Netbeans.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
<mailto:users-unsubscr...@netbeans.apache.org>
For additional commands, e-mail:
users-h...@netbeans.apache.org
<mailto:users-h...@netbeans.apache.org>
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
