Hi Chad et. al,
> It seems that lots of things in the maven world make the assumption
> that the aggregator pom and the parent pom are one and the same.
Indeed, there are some issues with it. For example:
http://jira.codehaus.org/browse/MNG-4687
Regards,
Curtis
On Tue, Nov 13, 2012 at 12:1
> > Concerning the empty "relativePath" element, this will typically be
> > empty when you can't guarantee that the parent is in the parent
> > directory. it's a common practice to separate the responsibilities of
> > the aggregator pom from the parent pom. When that is the case, if you
> > don'
On Mon, Nov 12, 2012 at 1:42 PM, David Karr wrote:
> Concerning the empty "relativePath" element, this will typically be empty
> when you can't guarantee that the parent is in the parent directory. it's
> a common practice to separate the responsibilities of the aggregator pom
> from the parent p
Concerning the empty "relativePath" element, this will typically be empty
when you can't guarantee that the parent is in the parent directory. it's
a common practice to separate the responsibilities of the aggregator pom
from the parent pom. When that is the case, if you don't have the empty
"rel
Hi
Why do you use an empty element?
If the parent is in the directory above the current project, then just
omit the element. Otherwise it must contain the relative
path to the directory where the parent pom is.
On 2012-11-01 23:10, Andre Gomes wrote:
>
> I am using the maven-site-plugin versi
I am having the same error here, but no clue on the cause.
Marcelo
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-site-can-not-find-parent-tp5729099p5730240.html
Sent from the Maven - Users mailing list archive at Nabble.com
