I posted a reply to this on stackoverflow, since that's where you included more details. The bottom line was that the properties are *not* defined in A or B, only in *profiles* in A and B. And there's the rub: those profiles do not apply when building C, and the property is not defined anywhere in C's pom.
On Sat, Nov 13, 2010 at 11:42 AM, cowwoc <[email protected]> wrote: > > Hi, > > I've posted a simple testcase at > http://stackoverflow.com/questions/4171222/maven-depending-on-inheriting-artifact-causes-build-error > that demonstrates how POM inheritance causes builds to break. > > Given three POM files: > > * C depends on B. > * B inherits from A. > * I can build A and B > * C fails to resolve properties defined in A or B, and as a result fails > to locate its transitive dependencies. The build breaks. > > Please help! > > Thanks, > Gili --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
