Re: Parent pom and site (was Re: svn commit: r731428)

On Mon, Jan 5, 2009 at 1:31 AM, Henri Yandell <[email protected]> wrote:
> On Sun, Jan 4, 2009 at 7:50 PM, Rahul Akolkar <[email protected]> wrote:
>> On Sun, Jan 4, 2009 at 10:39 PM,  <[email protected]> wrote:
>>> Author: bayard
>>> Date: Sun Jan  4 19:39:53 2009
>>> New Revision: 731428
>>>
>>> URL: http://svn.apache.org/viewvc?rev=731428&view=rev
>>> Log:
>>> Making the pom a child of the taglibs-parent. Wondering if there's any reason for keeping the site separate.
>>>
>> <snip/>
>>
>> Yup, we want the pom to stand by itself. That way its easier to release.
>
> I kind of went with that. The site.xml is there with the pom (no
> arguments expected). However, I also have the index.html with the
> parent pom and the rest of the site is in a site/ subdirectory that is
> a sibling to the other components. Having pootled on a bit further
> though with the fun that is Maven2 site plugin url trickery, I suspect
> I could put it back in the site and move all the rest down into a site
> directory.
>
<snip/>

site.xml with pom is good. How much you want to fight m2 for the URLs
etc. is ofcourse upto you, but its known to be tricky. I like a
Commons-like setup (having just worked on those sites today, its as
convenient as a site for a project with many components is going to
get I think).

Having said that, as long as you can produce a reasonable recipe for
updating the site thats great (and an improvement over the current
setup, thanks for that). I think the major requirements have to do
with loose coupling and common tasks (may be obvious, but thinking
aloud):

 * It should be possible to update a component site (without requiring
an update of the main project site)
 * Similarly, it should be possible to update the main site independently
 * Common tasks should be straightforward (such as updating download
pages, lets say it becomes frequent at some point :-)

-Rahul