Yep! which was why I had only <relativePath> which would force you to check out the parent.
i.e. it would be a child that _cannot_ be build without the parent, for use by developers the release plugin would (on the version tagged for release) replace the <relativePath> tag with the released parent's identification triplet (or quartet if you're mad and have a classifier too) so that releasing the parent will give a stand-alone module that can build on it's own, but the trunk poms would not change On Jan 30, 2008 9:19 AM, Heinrich Nirschl <[EMAIL PROTECTED]> wrote: > On Jan 30, 2008 8:59 AM, Erez Nahir <[EMAIL PROTECTED]> wrote: > > I also think as Stephen, > > > > Having an option to specify parent with relative path will be very > helpfull, > > I'm sure a solution can be found to provide this functionality. > > Maybe something like having both <relativePath> and <version> and give > > precedence to <relativePath> such that if it is found, it will be used > and > > if not, the <version> will be used instead... > > > > Erez. > > This would give different results when the whole tree is checked out > vs. just the module is checked out. > > - Henry > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
