Bruno Melloni <b...@melloni.com> wrote: > First, you are right... I misread. When I look at the maven plugins in > pluginManagement I see v2 and v3: clean=3.1.0, compiler=3.8.1, > surefire=2.22.1, jar=3.0.2, install=2.5.2, deploy=2.8.2, site=3.7.1, > project-info-reports=3.0.0. Still, it is > 2.0 so LATEST is no longer > supported as a version tag.
As far as I know there is no direct relation between Maven plugin versions and the version of Maven itself. If you add the -V flag to your build command the version of Maven itself will be printed. Or run Maven with just the -v if you want the Maven version without running a build. > (1) IntelliJ is caching the JARs it uses for a project somewhere. And giving > it the commands to reload dependencies or the POM fail if the version number > has not changed... since I am seeing a file from January. Also, the IntelliJ > setting "Always update snapshots" fails as well. This may be a Maven issue > or it might be a quirk of IntelliJ, my suspicion is that IntelliJ relied on > the old 2.x maven behavior for that setting. Sadly I am not knowledgeable > enough to know. And what happens when you build the apps using Maven directly instead of using IntelliJ? > (2) Looking for an alternative all I found for 3.0 and above Maven was the > use of version ranges in the dependency entry of the app2 POM. That would > require updating the version after even a tiny change in app1, but at least > it would not require updating the version in the the pom of the myriad of > "app2"s that we have, unless we wanted to. I suspect this is what > versions-maven-plugin does but that I botched it when I tried to use it, as > its documentation is very confusing for a beginner and they don't provide a > single complete example of a POM that uses it. The symptom was an error > popping up in the POM itself, long before trying to do a build. I think the > error was either the "<version>[0.0.1, 0.0.999)-SNAPSHOT</version>" tag, or > my missing something in plugin management. I don’t know if <version>[0.0.1, 0.0.999)-SNAPSHOT</version> is valid syntax, but if it is, then I would recommend not using it. (I generally would stay away from using version ranges in general, because it screws up reproducible builds.) As long as you’re using a snapshot version for the app1 dependency in app2 you should not need to bump the dependency version when making changes to app1. Nils. P.S. Maybe off-topic, but what is your use case for one app depending on another? I’d generally use a library dependency to share functionality between multiple apps. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
