I ran into this a while ago too. Since I don't actually need my parents to be called "parent", I just renamed them to match the directory structure. The other workaround is that in each pom you specify the scm url, tagbase and site url.
-----Original Message----- From: Julian Payne [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 15, 2006 4:25 AM To: users@maven.apache.org Cc: Julian Payne Subject: Path when doing site-deploy includes parent artifactId When I deploy my site using the site-deploy goal it adds the parent artifactId. I have a pom as follows: <project> <modelVersion>4.0.0</modelVersion> <parent> <groupId>jviews</groupId> <artifactId>jar-template</artifactId> <version>SNAPSHOT</version> </parent> <name>ILOG JViews Utilities</name> <artifactId>jviews-utilities</artifactId> ... </project> When I do site-deploy it deploys to ${distributionManagement.site.url}/jar-template/jviews-utilities !!! How can I specify that I do not want the extra "jar-template" directory that corresponds to the parent "artifactId"? I have the same problem when loading the pom into continuum. Thanks, Julian Payne ILOG --------------------------------------------------------------------- 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]
