Congrats guys! Can be worth some more noise cause I have to admit I didn't see mvnd before this thread and it is something all dev likely want to test "locally" (vs on a CI where you don't want it) IMHO.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le ven. 16 oct. 2020 à 16:15, Peter Palaga <ppal...@redhat.com> a écrit : > Re-layouting the mvnd distro worked indeed, see > https://github.com/mvndaemon/mvnd/pull/96 . Many thanks for the > suggestion, Romain! > > mvnd and stock Maven will be able to continue their peaceful co-existence > :) > > -- P > > On 14/10/2020 10:20, Peter Palaga wrote: > > On 14/10/2020 08:20, Romain Manni-Bucau wrote: > >> Hi, > >> > >> This one is not easy since both cases make sense IMHO (using "mvn" > >> through > >> mvnd or real pure isolated "mvn"). > >> My immediate thought is to play with PATH order and to provide an "mvn" > >> script as an extension of mvnd and not something built-in (well > >> documented > >> it is enough IMO). > > > > Yeah, recommending users to put the stock Maven's bin before mvnd's was > > was what we were thinking about. The caveat is that e.g. SDKMAN iterates > > over packages in alphabetic order, prepending the individual bin folders > > to the PATH. mvnd/bin thus gets a higher precedence than maven/bin > > > >> Using toolchain we can also make it more transparent (but not sure it > >> would > >> be the default without some enhancements and plugin upgrades which seems > >> the issue you hit). > >> > >> Last thing I can think about is to relayout the distribution: mvnd/bin > >> does > >> not contain maven but set maven.home to a folder not in path with mvn > >> script. > > > > That sounds viable, we should try that. Thanks for the idea! > > > > -- P > > > >> This makes mvnd in PATH but not mvn script since a lot of mvn script > >> lookup > >> is done in mojo reading maven.home - if not it can/should be fixed since > >> maven/bin does not have to be in PATH to work. Such "conflict" is very > >> acceptable since it is exactly the goal of mvnd IMHO and it does not > >> break > >> OS setup. > >> > >> Hope it makes some sense. > >> > >> Romain Manni-Bucau > >> @rmannibucau <https://twitter.com/rmannibucau> | Blog > >> <https://rmannibucau.metawerx.net/> | Old Blog > >> <http://rmannibucau.wordpress.com> | Github > >> <https://github.com/rmannibucau> | > >> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > >> < > https://www.packtpub.com/application-development/java-ee-8-high-performance> > > >> > >> > >> > >> Le mer. 14 oct. 2020 à 01:02, Mark Derricutt <m...@talios.com> a écrit > : > >> > >>> I just wanna say kudos to mvnd - found it the other day on r/java (or > >>> r/programming) and I must say - this is awesome. > >>> > >>> It even plays well with our tiles-maven-plugin which I was sure it > would > >>> play up on. > >>> > >>> Mark > >>> > >>> > >>> > >>> > >>> From: Peter Palaga <ppal...@redhat.com> <ppal...@redhat.com> > >>> Reply: Maven Developers List <dev@maven.apache.org> > >>> <dev@maven.apache.org> > >>> Date: 14 October 2020 at 8:55:14 AM > >>> To: dev@maven.apache.org <dev@maven.apache.org> <dev@maven.apache.org> > >>> Cc: Guillaume Nodet <gno...@redhat.com> <gno...@redhat.com> > >>> Subject: Hello from mvnd > >>> > >>> I think we can say that the project left the PoC phase recently. We > >>> use it > >>> for our daily work, we made it available via SDKMAN and we are solving > >>> issues coming from the users. > >>> > >> > > > >
