from the module's perspective |-- my-module | `-- pom.xml `-- parent `--
pom.xml<BR>
The Solution<BR>
To address this directory structure (or any other directory structure), we
would have to add the <relativePath> element to our parent section.<BR>
<project>
<parent>
<groupId>com.mycompany.app</groupId>
<artifactId>my-app</artifactId>
<version>1</version>
<relativePath>.../parent/pom.xml</relativePath>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>my-module</artifactId>
</project><BR>
relativePath will allow the module to locat parent
pom<BR>http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
<BR>HTHMartin______________________________________________ Disclaimer and
confidentiality note Everything in this e-mail and any attachments relates to
the official business of Sender. This transmission is of a confidential nature
and Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within this
transmission. > Date: Tue, 2 Sep 2008 10:54:14 +0930> From: [EMAIL PROTECTED]>
To: [email protected]> Subject: Organization & Site Skin Module> > Hi
All,> > I have> > company/pom.xml (module = skin)> company/skin/pom.xml (parent
= company)> > Also, the company/src/site/site.xml (skin = comany-skin).. this
is what sets> the organizational skinning of site's.> > When I do a release...
the company site fails to build because it can't> locate the site skin in any
repo. I'm guessing that the deploy of the> release is AFTER the site - hence
the skin can never be applied until the> module is deployed.> > yes/no... I'm
having a guess either way.> > Cheers.
_________________________________________________________________
Get ideas on sharing photos from people like you. Find new ways to share.
http://www.windowslive.com/explore/photogallery/posts?ocid=TXT_TAGLM_WL_Photo_Gallery_082008
