Currently, no. Adding the parents as dependencies though is a little scary because it could cause some recursion in transitive dep resolution. You can however use dependency:copy or unpack and list them in the artifactItems list to do what you want.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Keith Bonawitz Sent: Thursday, May 08, 2008 12:06 PM To: Maven Users List Subject: dependency:copy-dependencies and parent projects Is there any way for dependency:copy-dependencies and dependency:unpack-dependencies to consider parents (and all ancestors) as dependencies? Alternately, is there a way to automatically/implicitly add the parent the parent as a dependency? I tried adding: <dependencies> ... <dependency> <groupId>${project.parent.groupId}</groupId> <artifactId>${project.parent.artifactId}</artifactId> <version>${project.parent.version}</version> <scope>compile</scope> <type>pom</type> </dependency> </dependencies> To a common ancestor pom for my organization's projects, but this resulted in errors: 'dependencies.dependency.artifactId' with value '${project.parent.artifactId}' does not match a valid id pattern. 'dependencies.dependency.groupId' with value '${project.parent.groupId}' does not match a valid id pattern. Thanks so much to this community for all the help the last couple days, Keith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
