Option 1: go ahead and put a full configuration in this POM, and then make sure that all of the things that use it really do over-ride it.
Option 2: Give it a parent or child: create a project with a site just to document and aggregate this, with enough SEO to catch googles. Option 3: take up my elaborate suggestion in the mixin thread. On Sun, Jun 26, 2011 at 4:02 AM, Hervé BOUTEMY <[email protected]> wrote: >> Now the question is: where do we put ASF pom documentation? > sharing a few thoughts: > 1. in the project itself? need to find a way to get its publication done > without tainting the pom > > 2. in the Maven site [1], in a dedicated directory > > 3. at the top of pom svn [2]: the main difference I see from Maven site is > that > we can configure project information specifically (issue tracking especially), > create dedicated menu > > any thought? > > Regards, > > Hervé > > [1] http://svn.apache.org/viewvc/maven/site/trunk/ > > [2] http://svn.apache.org/viewvc/maven/pom/trunk/ > > --------------------------------------------------------------------- > 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]
