No, this is not a must... You can link either way if you want, but there's
several things you have to consider:
If you build the 'parent' and it does not contain the 'modules'-tag, the
children DO NOT get build.
Just play around with it a bit, Maven is very flexible in this way. I do
however
If you build the 'parent' and it does not contain the 'modules'-tag, the
children DO NOT get build.
Yeah, we want to be able to build from either the parent (and build
everything) or from the child (and just build the child) but we need
the information in the parent when the child is being
How about re-writing the plugin to Maven2? Then you can at least remove
the 'modules'-part in your base-POM...
Otherwise I'm afraid you're indeed stuck with the 2-way dependency.
On Thursday 15 November 2007 12:34, Aaron Zeckoski wrote:
If you build the 'parent' and it does not contain the
On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote:
True. One question though: why do you use the 'relativePath'-attribute?
This
shouldn't be really necessary, or am I missing something here?
say you've just checked out a fresh project tree from svn - it's not yet
been
released to any
True. One question though: why do you use the 'relativePath'-attribute? This
shouldn't be really necessary, or am I missing something here?
On Thursday 15 November 2007 14:35, Stuart McCulloch wrote:
On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote:
How about re-writing the plugin to
On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote:
How about re-writing the plugin to Maven2? Then you can at least remove
the 'modules'-part in your base-POM...
Otherwise I'm afraid you're indeed stuck with the 2-way dependency.
also note the parent doesn't have to be the same as the
Understood, but if you have dependencies to you sibling-modules, you'd have
the same problem...
So, I'd personally always build from the root-project after a fresh
check-out... And from then on it wouldn't be necessary to use the
relativePath.
Still, I understand your reasoning and I agree
