If folks are willing to maintain a list of configured plugins in CMS, I (not that it matters a lot) don't object to shovelling all this into the CMS.
On Tue, Feb 8, 2011 at 9:51 PM, Brian Fox <[email protected]> wrote: > On Tue, Feb 8, 2011 at 9:45 PM, Benson Margulies <[email protected]> > wrote: >> I was somewhat squeamish about all of this, and now you've confirmed >> my fears. My theory was to have the doc remind inheritors to override. >> >> The good thing about the site plugin process is that there's some >> reasonable chance that anyone modifying the pom will modify the doc. >> If all the doc moves into the (a)ether of markdown, the chances of >> that happening drop precipitously. The bad thing, as you note, is >> unwanted inheritance. I suppose that someone could see this as a >> design issue for maven that it's not so easy to set up a doc site for >> a parent pom without dribbling all over the projects that use it. >> >> The other reason I thought that the site plugin was clever was to get >> the pluginManagement reporting, so that people could easily see what >> managed versions of what plugins were coming from this parent. >> >> Having to submit patches to the infra site every time seems >> particularly painful, but if enough mvn committers are also infra >> committers, I guess it won't kill anyone. Converting the APT to >> markdown might. Ripping these goodies out of this POM and replacing >> them with a big fat comment pointing to wherever the doc actually >> lives is, I suppose, the next best thing. >> >> I'm willing to try to be helpful again within the limits of my lack of >> karma here. >> > > Having a site for the pom just feels like overkill to me for what is > really just one useful page. I think the infra CMS is better for this > and it can go along with the release doco I put in place last year. > > Alternatively, we can factor all of this down to a separate module > asf-site similar to what we do for the maven site (notice the maven > site isn't part of the maven pom for the same reasons). This would be > a better option than what is in place imo, but my gut is that the CMS > is best. > >> >> On Tue, Feb 8, 2011 at 9:34 PM, Brian Fox <[email protected]> wrote: >>> I see now what you've done. If you need these values for the site, >>> then drop them into the asf-pom profile you created, but honestly I >>> think we should move all of this and the site.xml out and find a place >>> to put the docs into the infra site, or somewhere inside of maven. I >>> think the asf pom project needs to be JUST the pom so that nothing >>> inherited screws with anyone else's projects. >>> >>> On Tue, Feb 8, 2011 at 9:29 PM, Brian Fox <[email protected]> wrote: >>>> same comment as the url, i don't think we want to be polluting the >>>> inheritence tree with specifics about the ASF wide pom project. >>>> >>>> On Sat, Feb 5, 2011 at 3:47 PM, <[email protected]> wrote: >>>>> Author: olamy >>>>> Date: Sat Feb 5 20:47:25 2011 >>>>> New Revision: 1067520 >>>>> >>>>> URL: http://svn.apache.org/viewvc?rev=1067520&view=rev >>>>> Log: >>>>> [MPOM-7] add issueManagement to https://issues.apache.org/jira/browse/MPOM >>>>> >>>>> Modified: >>>>> maven/pom/trunk/asf/pom.xml >>>>> >>>>> Modified: maven/pom/trunk/asf/pom.xml >>>>> URL: >>>>> http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?rev=1067520&r1=1067519&r2=1067520&view=diff >>>>> ============================================================================== >>>>> --- maven/pom/trunk/asf/pom.xml (original) >>>>> +++ maven/pom/trunk/asf/pom.xml Sat Feb 5 20:47:25 2011 >>>>> @@ -53,6 +53,10 @@ under the License. >>>>> <url>http://www.apache.org/</url> >>>>> </organization> >>>>> <url>http://www.apache.org/</url> >>>>> + <issueManagement> >>>>> + <system>jira</system> >>>>> + <url>https://issues.apache.org/jira/browse/MPOM</url> >>>>> + </issueManagement> >>>>> <repositories> >>>>> <repository> >>>>> <id>apache.snapshots</id> >>>>> >>>>> >>>>> >>>> >>> >>> --------------------------------------------------------------------- >>> 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] >> >> > > --------------------------------------------------------------------- > 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]
