generally you don't need to use that relativePath tag.. and your second scenario still looks a little odd.
I think maybe your not installing your superpom into the repository before you start building your project? Normally if your doing something like this with a company pom, then that pom is managed separately in its own scm setup.. in svn this would be .../repos/company/trunk/pom.xml .../repos/company/tags/company-1/pom.xml .../repos/company/tags/company-2/pom.xml etc. Those pom.xml in the company-1 and company-2 would be released and available in some repository as any other artifact or pom resource in maven. Then you project would just reference that company pom via the groupId:artifactId:version and maven would take care of all the work. that make more sense? jesse On 7/25/07, javijava <[EMAIL PROTECTED]> wrote: > > > Someone use the tag relativePath with success? > > I try to use this tag, with "../" and "../../", but it does not work. (At > least for me). > Continuum ever said: "URL malformed". I use first 1.0.3 and after > 1.1-alpha-2 version with the same result. > > finally I change the struct and put a pom in each level, but i dont know if > this is rigth > > > I change : > > > Repo > | > |----Parent--------Pom.xml ( SuperPom) > | > |----P1 > | | > | |------Trunk > | | \------- Pom.xml (project) > | \------Release > | > | > > to: > > > Repo > | > |----Pom.xml ( SuperPom) > | > |----P1 > | |------Pom.xml (connector) > | |------Trunk > | | \------- Pom.xml (project) > | \------Release > | > | > > What do you think about? > > regards > > > -- > View this message in context: > http://www.nabble.com/relativePath-tf4140573.html#a11777693 > Sent from the Continuum - Users mailing list archive at Nabble.com. > > -- jesse mcconnell [EMAIL PROTECTED]
