Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.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)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C77599.42CB2B5D"
Subject: [Vote] Move plugin site.xml up to Maven or Shared
Date: Mon, 2 Apr 2007 22:39:08 -0400
Message-ID: <2BABBE7D2A66E04DB8A66A527D29927E25E1D1@intrepid.infinity.nu>
Thread-Topic: [Vote] Move plugin site.xml up to Maven or Shared
Thread-Index: Acd1mUFUvHeyMMDRRFew3HWUZd9kIA==
From: "Brian E. Fox" <brianf@reply.infinity.nu>
To: "Maven Developers List" <dev@maven.apache.org>

------_=_NextPart_001_01C77599.42CB2B5D
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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.


------_=_NextPart_001_01C77599.42CB2B5D--