Re: Build fails due to dependency not found (removed) even if a most recent one is available...

Hi Delany thanks for the answer. No I am not assuming the later versions are backward compatible, but we realised that they were (we had tests giving us this feedback). I was asking that question, because we didn't put any hard requirement for that version as explained here

Re: Build fails due to dependency not found (removed) even if a most recent one is available...

Hi Robert, You're assuming later versions are backward compatible. That's a dangerous assumption. If there are conflicting transitive dependencies in your dependency tree, you should sort them out. Would you rather have a ClassNotFoundException at runtime, or a build error? If L requires version 1

Re: Build fails due to dependency not found (removed) even if a most recent one is available...

Thanks Delany, but just for my knowledge, why maven is not able to determine that because you are using the newer library, you can avoid failure? Is it because maven has to download all dependencies before applying the resolution of the most recent version? Can we then say that "removing old depend

[ANN] Maven Compiler Plugin 3.9.0 released

The Apache Maven team is pleased to announce the release of the Maven Compiler Plugin version 3.9.0. https://maven.apache.org/plugins/maven-compiler-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-compiler-plugin 3.9.0 Rel

Re: Ambari 2.7.6 build questions

Maven profiles are not active by default. Run "mvn validate -Psources" and check again for the source-maven-plugin. Rather don't edit files in Maven local repository. If you must add them, use the dependency plugin like so `mvn dependency:get -Dartifact=org.apache.maven:sources-maven-plugin:3.2.1:j

RE: Ambari 2.7.6 build questions

Thanks. You are clearly helpful. If I may prod you regarding manual download/install of items in .m2 When I originally initiated the project (following ambari docs) and used: mvn versions:set -DnewVersion=2.7.6.0.0 and again for ambari-metrics a bunch of things got downloaded. When I ran clea

Re: Ambari 2.7.6 build questions

Hi Marc, The "2.1.4" line should be left out. Clearly the authors are not following standard practice for managing dependencies, so do not assume that they know what they're doing. Change the version in the dependencyManagement section if you need it to be v2.1.4. Delany On Wed, 12 Jan 2022 at 12

Ambari 2.7.6 build questions

HI all, I get a ‘overriding managed version 2.0.1 for rpm-maven.plugin’ message and I see two plugin definitions for this artifact, with two versions, in the same ‘build’ block in the top-level (ambari-2.7.6.0.0) POM. From what I see, does this mean that the plugin must be declared in both plac

[ANN] Apache Maven SCM 2.0.0-M1 released

The Apache Maven team is pleased to announce the release of the Apache Maven SCM, version 2.0.0-M1. https://maven.apache.org/scm/ Release Notes - Maven SCM - Version 2.0.0-M1 ** Bug * [SCM-883] - ScmFileSet DEFAULT_EXCLUDES too restrictive * [SCM-973] - GitCheckInCommandNoBranchTest f

[ANN] Maven JAR Plugin 3.2.2 released

The Apache Maven team is pleased to announce the release of the Maven JAR Plugin version 3.2.2. https://maven.apache.org/plugins/maven-jar-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-jar-plugin 3.2.2 Release Notes - Ma