When you put versions into those dependencies in your ear project, and *then* run `mvn help:effective-pom`, to you see the dependencyManagement section?
If not, there is something wrong with your parent specification...it may be something as simple as not using a <relativePath/> where the others are, and your parent POM isn't installed in the local repository... At any rate, checking that first suggestion with effective-pom should help determine whether inheritance is happening for this child project. -john On 6/6/06, Lee Meador <[EMAIL PROTECTED]> wrote:
Alexandre, Thanks. I did check the <parent> section in the problem project. It is there and is exactly like the <parent> section in some of the other children that do work. Also, the fact that other child projects are dependant on the same children used in the problem project, and everything works fine in those projects suggests that the dependencyManagement ids are ok. Else those other projects would have the same problem. -- Lee On 6/5/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > Look like there is a mistake in your ear pom. My guess : you probably > forgot to add the parent section or you made a mistake in the ids you > supplied in the parent pom dependencyManagement section. > > On 6/5/06, Lee Meador <[EMAIL PROTECTED]> wrote: > > 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] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- Lee Meador Sent from gmail. My real email address is [EMAIL PROTECTED]
