The answer is... yes! Simply remove the relative path information. For example:
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <parent> <groupId>com.biomedcentral.organization</groupId> <artifactId>organization</artifactId> <version>1.1-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>com.biomedcentral</groupId> You just have to make sure that the pom you are referencing is published in a repository that the build environment has access to, and it will download the pom just like any other dependency. G > -----Original Message----- > From: shevit [mailto:[EMAIL PROTECTED] > Sent: 12 October 2006 15:04 > To: continuum-users@maven.apache.org > Subject: "company pom" problem > > > > Hi, > > We are facing a problem with multi module maven2 projetcs > with a super-POM > defined at the company level. > It's ok to store modules in subdirectories of the project. But the > organisation POM is shared between multiple projects, it > cannot be placed at > the parent directory level of each of them. Also, company POM does not > define it's projects as modules. It lives it's own life in the maven2 > repository. > > So, when we are uploading the project POM to Continuum (using > URL), it looks > for the company POM in "./.." > > Is there any way to exclude the organisation POM from > continuum and let > maven2 download it from the remote repository? > > Do you see another solution for this problem? > > Thanks a lot, > Vitaliy Shevchuk > -- > View this message in context: > http://www.nabble.com/%22company-pom%22-problem-tf2430528.html > #a6776852 > Sent from the Continuum - Users mailing list archive at Nabble.com. > >
