On 9/14/06, Tom Hurley <[EMAIL PROTECTED]> wrote:
Hi:I am new to Maven so this issue is probably due to a misunderstanding on my part so any help would be greatly appreciated. I have a multi-level project structure (4 levels) i.e. applications--> common --> server --> project 1 ... --> project n --> client --> project 1 ... --> project m Each project (lowest level) produces a jar file so the packaging in each of their pom files is set to jar. There is a pom file at each level whose packaging is set to pom so that I can inherit settings and plugins at each level from the level above. Everything works fine when I am at the project (i.e. lowest) level in my tree. If however, I am at, say the server level (one level up from the project level) and I want to do a 'mvn package' to package all of the projects underneath I get the following error message: This kind of makes sense, since the packaging for the pom file at this level is not going to create anything to be placed in the repository, or does it?
Actually, <packaging>pom</packaging> projects are installed in the repository too. When a project goes to inherit properties from a parent POM and isn't being run from the parent, the parent POM is looked up in repositories, starting locally and working out, just like any other dependency.
How can I achieve what I am trying to do? i.e while at any level be able to run mvn on all levels underneath when the pom at the level I'm working at has a parent? In my first iteration I only had 2 levels and I was able to run mvn at the top level for the level underneath.
'mvn install' the top-level project to ensure all the POMs are in your local repository. After that all the children should be able to locate their parents as needed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
