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.
Jboss 7.x redeploy option
Multiple Sources directories using maven-remote-resources-plugin
Skip compilation of integration test in maven project
No setter found for property 'kBaseName' in class 'org.kie.spring.factorybeans.KBaseFactoryBean'
Run JMeter headless with maven with AMQP plug in
Can I get Maven to turn a file into properties I can use in my Maven script?
Deploy an artifact into Archiva repo using maven POM
Alternative place to specify mvn --fail-at-end command line option?
Maven - Not able to open jars it is downloading
Deploy p2 repo to Nexus
System.Diagnostics.Debug.WriteLine() Does Not Work Under NUnit Console
how to use maven with intellij 13
Automatically download missing artifacts if missing in Artifactory
How to package up a leiningen project for recompilation with all the libraries included? [for users without an internet connection]
How to fail when maven profile does not exist?