Return-Path: Delivered-To: apmail-maven-dev-archive@www.apache.org Received: (qmail 41785 invoked from network); 5 Apr 2007 21:28:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Apr 2007 21:28:57 -0000 Received: (qmail 20140 invoked by uid 500); 5 Apr 2007 21:29:02 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 20081 invoked by uid 500); 5 Apr 2007 21:29:02 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 20069 invoked by uid 99); 5 Apr 2007 21:29:02 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 14:29:02 -0700 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (herse.apache.org: transitioning domain of brianf@reply.infinity.nu does not designate 205.210.42.54 as permitted sender) Received: from [205.210.42.54] (HELO mx-outbound01.easydns.com) (205.210.42.54) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 14:28:54 -0700 Received: from intrepid.infinity.nu (c-24-128-239-207.hsd1.nh.comcast.net [24.128.239.207]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx-outbound01.easydns.com (Postfix) with ESMTP id DD0F27FC5 for ; Thu, 5 Apr 2007 17:26:07 -0400 (EDT) Subject: RE: [Vote] Move plugin site.xml up to Maven or Shared Date: Thu, 5 Apr 2007 17:28:32 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: <2BABBE7D2A66E04DB8A66A527D29927E25E1FE@intrepid.infinity.nu> In-Reply-To: <2BABBE7D2A66E04DB8A66A527D29927E25E1D1@intrepid.infinity.nu> Content-class: urn:content-classes:message X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-TNEF-Correlator: Thread-Topic: [Vote] Move plugin site.xml up to Maven or Shared Thread-Index: Acd1mUFUvHeyMMDRRFew3HWUZd9kIACLghNQ References: <2BABBE7D2A66E04DB8A66A527D29927E25E1D1@intrepid.infinity.nu> From: "Brian E. Fox" To: "Maven Developers List" X-Virus-Checked: Checked by ClamAV on apache.org Binding: +6(Brian, John, Dennis, Brett, Jason, Emmanuel) Non-Binding: + 3(Andy,John T, Maria) I will make the changes and stage the main site before pushing it out. What are we doing with the links that are present on plugins but not on the main site? It seems to me that they should be the same in both locations (either with or without). -----Original Message----- From: Brian E. Fox [mailto:brianf@reply.infinity.nu]=20 Sent: Monday, April 02, 2007 10:39 PM To: Maven Developers List Subject: [Vote] Move plugin site.xml up to Maven or Shared Currently only plugins get a nice looking skin that matches the main maven.apache.org page because the site.xml exists in the plugin project. Other things like shared get a homely looking default skin. I see two options here: =20 1. Move the site.xml up to the maven pom. This is preferred so that all submodules of maven can get the standard skin and override it if they choose.=20 2. Copy the site.xml over to the shared pom. This is less intrusive but doesn't cover all submodules that come along. =20 Vote: [ X ] Move to Maven Pom [ ] Copy to shared =20 Vote is open for 72 hrs. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org