The relative path doesn't necessarily work once deployed. And its not guaranteed to be true -- you could checkout just the module rather than the entire project, and suddenly Maven can't find that parent since the relativePath is no longer accurate.
If anything, I'd argue that relativePath should perhaps be removed. Wayne On 5/7/07, David Corbin <[EMAIL PROTECTED]> wrote:
On Sunday 06 May 2007 19:20, Bryan Loofbourrow wrote: > I believe that you are correct about not being able to parameterize the > project parent tag, or so a co-worker tells me. He conjectures that the > parent resolution is required before resolution of property names. That > makes sense, since, in general, the value you're looking for could be > defined in the parent pom, But when I provide a <relativePath> tag in parent declaration, that should allow be enough. In fact, if I provide r<relativePath> all the artifact information provided should just be a safety check. David --------------------------------------------------------------------- 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]
