Note that the question is regarding the lowest version and
functionality/plugins it supports. A developer may install any later
version. With that I am inclined to bump version to 3.3.1 unless there
are other required/useful features supported by later version.
+1 for 3.3.1.
Thank you,
Vlad
On 5/16/18 13:11, Ananth G wrote:
My understanding is that we might be using the various config files support
- .mvn/jvm.config
- .mvn/mvn.config
version 3.5.0 allows for a manual override of the mvn config values from
the command line if the local development process needs it to be the case.
Hence +1 for 3.5.0
Plus 3.5.x seems to provide additional goodies like colour outputs as well
as a module progress indicators.
Regards,
Ananth
On Thu, May 17, 2018 at 5:29 AM, Yogi Devendra <yogideven...@apache.org>
wrote:
1. +1 for 3.3.9.
2. Why do we need 3.5.x if 3.3.9 serves the purpose?
~ Yogi
On 16 May 2018 at 20:20, Ananth G <ananthg.a...@gmail.com> wrote:
+1 for maven version upgrade.
+1 for version 3.5.x as there seems to be some fixes for issues related
to
this property in version 3.3.9
https://issues.apache.org/jira/browse/MNG-5786 ?
Regards,
Ananth
On Wed, May 16, 2018 at 5:13 AM, Vlad Rozov <vro...@apache.org> wrote:
I think it is time to revisit minimum maven version required to build
Apex. I suggest upgrading to 3.3.1 at minimum to get
maven.multiModuleProjectDirectory property supported. Another option
is
to upgrade to 3.5.x.
Thank you,
Vlad
