Hi Ben,
I've got the same problem.
As you've noted the Hudson Maven-generated site appears to be the last
pom/module built and not the highest parent. Also, the use of a url based on
${project.groupId} and ${project.artifactId} is ugly very ugly.
Especially when you get two level's deep on
Is there a Hudson plugin to add a random link to the Hudson screens? If so
you can point it to the base of whereever you deploy the site. Just remember
to use that link instead of the one Hudson calls site.
-- Lee
On Tue, May 26, 2009 at 3:10 PM, B Smith-Mannschott
bsmith.o...@gmail.comwrote:
I'm sending this missive to user's lists of both hudson and maven
because it concerns using these two tools together, and I'll need help
from both parties to make this work.
Rather than separately site-deploying the sites of the 30 or so maven
projects hudson is building for me at work, I've