Takari Maven Wrapper and Plugin
Hello all, We are pleased to announce a new release of the Maven Wrapper (0.2.1) and the Takari Maven Plugin (0.4.1) with the helping wrapper goal to install the Maven Wrapper in your project. The new release brings numerous changes that bring the wrapper up to using Maven 3.5.0, add support for numerous shell systems and operating systems and a number of other improvements. Please have a look at the changelogs and documentation in both repositories for further information on changes, usage and more. https://github.com/takari/maven-wrapper https://github.com/takari/takari-maven-plugin Manfred and numerous other helpers - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Shell
jline3 integration is in the works right now. https://github.com/jdillon/gshell/pull/8 manfred Paul King wrote on 2017-04-20 16:08: > OK, cool. Is the jline3 integration likely before the final? > > Cheers, Paul. > > On Fri, Apr 21, 2017 at 8:05 AM, Manfred Moser > wrote: >> This is a snapshot (=development) build - so no. >> >> Manfred >> >> Paul King wrote on 2017-04-20 14:30: >> >>> Nice Jason. Is it available via sdkman? >>> >>> Cheers, Paul. >>> >>> On Thu, Apr 20, 2017 at 4:08 PM, Jason Dillon wrote: Folks, just a quick not that I’ve updated Maven Shell for the latest release, can be found with the latest SNAPSHOT: https://oss.sonatype.org/content/repositories/snapshots/com/planet57/maven/shell/dist/mvnsh-assembly/1.2.0-SNAPSHOT/ Locally seems to be fully functional. I’ve been updating GShell (which mvnsh is based on) as well. I’m considering augmenting the release versions of mvnsh to match the upstream versions. I’m also eventually gonna update the jline support as I think jline3 is much much improved, thanks to gnodet, but I haven’t done that yet. If there are folks that may still be using older versions of the shell, I’d like to ask them to test the latest SNAPSHOTS and report back any issues. Cheers, —jason >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: understanding maven version resolution: minor and snapshots
Hi Jörg, As far as I know, Maven has no notion of "major" vs. "minor" vs. "patch" versions in the style of e.g. SemVer. It simply judges which version is the newest via its algorithm, and uses the newest, since it is assumed that a dependency on e.g. 3.2.0 means "version must be at least as new as 3.2.0". Regards, Curtis -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden On Fri, Apr 21, 2017 at 6:18 PM, Jörg Wille wrote: > In a project 2 "different" versions of the same library A are used. One, as > a direct dependency with a snapshot version *3.2.1-SNAPSHOT* and the same > library - but with version *3.2.0* - is being used as a transient > dependency in yet another library B. So, the 2 dependencies of A only > differ in the minor version. > When I build/install this project only the 3.2.1-SNAPSHOT version of > library A gets downloaded. > Is this correct behaviour for maven since it evaluates the 3.2.1-SNAPSHOT > to be compatible with the 3.2.0 release version or should maven download > the 3.2.0 release version since it is explicit mentioned as a transient > dependency in the pom of a library B? >
understanding maven version resolution: minor and snapshots
In a project 2 "different" versions of the same library A are used. One, as a direct dependency with a snapshot version *3.2.1-SNAPSHOT* and the same library - but with version *3.2.0* - is being used as a transient dependency in yet another library B. So, the 2 dependencies of A only differ in the minor version. When I build/install this project only the 3.2.1-SNAPSHOT version of library A gets downloaded. Is this correct behaviour for maven since it evaluates the 3.2.1-SNAPSHOT to be compatible with the 3.2.0 release version or should maven download the 3.2.0 release version since it is explicit mentioned as a transient dependency in the pom of a library B?
