From dev-return-104483-apmail-commons-dev-archive=commons.apache.org@commons.apache.org Fri Aug 03 19:37:11 2007 Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 44390 invoked from network); 3 Aug 2007 19:37:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Aug 2007 19:37:05 -0000 Received: (qmail 81150 invoked by uid 500); 3 Aug 2007 19:37:04 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 80683 invoked by uid 500); 3 Aug 2007 19:37:01 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 80674 invoked by uid 99); 3 Aug 2007 19:37:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2007 12:37:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tobrien@discursive.com designates 64.233.166.180 as permitted sender) Received: from [64.233.166.180] (HELO py-out-1112.google.com) (64.233.166.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Aug 2007 19:36:58 +0000 Received: by py-out-1112.google.com with SMTP id u52so1912964pyb for ; Fri, 03 Aug 2007 12:36:36 -0700 (PDT) Received: by 10.64.21.6 with SMTP id 6mr5721922qbu.1186169796127; Fri, 03 Aug 2007 12:36:36 -0700 (PDT) Received: by 10.64.209.5 with HTTP; Fri, 3 Aug 2007 12:36:36 -0700 (PDT) Message-ID: <7260cf030708031236q2593bbaen3b5eb7678f280e78@mail.gmail.com> Date: Fri, 3 Aug 2007 14:36:36 -0500 From: "Tim O'Brien" To: "Jakarta Commons Developers List" Subject: Re: [jxpath/all] Maven site help In-Reply-To: <600203.447.qm@web55103.mail.re4.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46B371EA.50604@apache.org> <600203.447.qm@web55103.mail.re4.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org On 8/3/07, Matt Benson wrote: > > --- Dennis Lundberg wrote: > > > Matt Benson wrote: > > > Thanks for your response, Dennis: > > > > > > --- Dennis Lundberg wrote: > > > > > >> The site for jxpath builds fine for me using > > Maven > > >> 1.0.2. It looks as > > >> good as any of the other components sites that > > are > > >> build with M1. > > >> > > >> Which reports that are generated is configured in > > >> the section > > >> of the file project.xml. Most of the plugins in > > >> Maven 1 can be tweaked > > >> by adding or changing properties in the file > > >> project.properties. > > >> > > >> If you need more info about a certain plugin, > > check > > >> the site for that > > >> plugin. Start at > > >> > > >> > > > > > > http://maven.apache.org/maven-1.x/plugins/bundledHistory.html > > >> and choose the plugin you're interested in. Each > > >> plugin has an item > > >> "Plugin properties" in the menu that gives more > > >> information. > > >> > > >> If you want to, we could convert the site to use > > >> Maven 2 instead. > > > > > > is there any reason I'd want to do that? > > :o > > > > > > Seriously, 'cause I don't know... > > > > The reason would be that commons is moving in that > > direction. It might > > be a waste of time for you to learn Maven 1 now, and > > then have to learn > > Maven 2 in a short while. You could just as well > > jump right on to Maven > > 2. But that's your call :-) > > Is the fact that the sites can be made uniform the > driving reason to use Maven 1 or 2? If, > hypothetically speaking, there were a third option > that could generate the site identically, would there > be a good reason to forbid its use? > Yes, standardization. Go ahead and create your own site generation technology, but commit to sticking around to update it forever. Commons project (especially) experience bursts of interest and activity. A project might have a dedicated release manager throughout the years (example would be Rahul and SCXML), but another project might have a release manager that disappears for a year, or a series of release managers spanning multiple years (example would be something like Codec). The only way certain subproject's sites are not going to fall into disrepair is if there is a common way to generate them. If a project has some custom site build process, it just makes it that much harder for someone to jump in and fix a bug and keep the documentation up to date. Instead of just turning you nose up on a Maven site, someone needs to create a commons-skin similar to what the Spring Framework guys are doing, and similar to what the Wicket people are doing. > -Matt > > > > > Anyway, I'm here if you need help with either > > version. > > > > > > > > -- > > Dennis Lundberg > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > dev-unsubscribe@commons.apache.org > > For additional commands, e-mail: > > dev-help@commons.apache.org > > > > > > > > > ____________________________________________________________________________________ > Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. > http://mobile.yahoo.com/go?refer=1GNXIC > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > -- ------ Tim O'Brien: (847) 863-7045 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org