I have a parent project/pom and several children using the form ../child1.
I put the versions for all the children projects in the parent pom (in dependencyManagement). They are all 1.0-SNAPSHOT. In all the child projects, when one depends on another, I don't put a <version> tag in the dependency section. In the child project for my ear, if I leave the <version> tag out, it complains "dependencies.dependency.version is missing" but the version is supplied in the parent's dependencyManagement section just like in all the other children. The other children have no problem. mvn help:effective-pom gives the same error about missing the dependency version. This only happens in the one child and only as relates to the other children (of the same parent pom) upon which it is dependent. (For example, the ear is dependent on one war project and two ejb jar projects.) The only change I have to make to build successfully is to add the <version> tags into the ear child project's pom. Does anyone have any ideas of where to look for this problem? -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
