maven
Why do I get invalid pom due to missing dependency.version although the version is managed?
I have case that looks like this: super dependency manangement of thrid-party parent-pom child of super projectA child of parent-pom dependency to third-party projectB child of parent-pom dependency to projectA projectA builds just fine, but when I try to compile projectB I get: [WARNING] The POM for [projectA] is invalid, transitive dependencies (if any) will not be available: 1 problems were encountered while building the effective model for [projectA] [ERROR] 'dependencies.dependency.version' for thrid-party.jar is missing. # Any idea why?
You need to install super to you local repo, just having relativePath set is not enough for this case.
Related Links
Sonatype Nexus 3 stuck on OnLine - Ready To Connect status for proxies
Jenkins get last test result when maven building fail
How can I make a goal optional in maven?
Cucumber Rerun failed features : Inconsistent filters: [#test1, #test, 23, 36]. Only one type [line,name,tag] can be used at once
Creating an external Maven packaging POM
How to Integrate BIRT Chart Engine 4.6.0 into maven project
Maven dependency plugin downloads POM instead of tar.gz
Maven get from Wrong repository
Artifactory Dependency Declaration does not match maven-metadata.xml or pom
Jenkins is not showing all executed Tests / Test Results in Build Overview
jBCrypt dependency not working
Maven not importing External Library into project after adding to .pom file in Intellij
docker-maven-plugin build assembly fail
Maven - How to override version?
Dependencies and Repositories?
DriverManager.getConnection never been executen in my maven project