Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 4462 invoked from network); 8 Feb 2004 18:25:20 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Feb 2004 18:25:20 -0000 Received: (qmail 75779 invoked by uid 500); 8 Feb 2004 18:25:05 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 75708 invoked by uid 500); 8 Feb 2004 18:25:05 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 75687 invoked from network); 8 Feb 2004 18:25:04 -0000 Received: from unknown (HELO minotaur.apache.org) (209.237.227.194) by daedalus.apache.org with SMTP; 8 Feb 2004 18:25:04 -0000 Received: (qmail 4211 invoked by uid 1339); 8 Feb 2004 18:25:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 Feb 2004 18:25:12 -0000 Date: Sun, 8 Feb 2004 10:25:12 -0800 (PST) From: Martin Cooper To: Jakarta Commons Developers List Subject: Re: [vote] Separate Directory for Commons Project files In-Reply-To: <40266E8B.6020807@latte.harvard.edu> Message-ID: <20040208101912.F766@minotaur.apache.org> References: <40266E8B.6020807@latte.harvard.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Sun, 8 Feb 2004, Mark R. Diggory wrote: > I don't want to make this change and step on anyones foot while doing it > so I'll put it to a vote. To recap: > > The issue involves consolidating the global commons build and site > generation files into their own directory within the jakarta-commons > project dir. > > Here is a list of the current files: > > /jakarta-commons/xdocs/ > /jakarta-commons/.cvsignore > /jakarta-commons/BUILD_DOCS.txt > /jakarta-commons/LICENSE > /jakarta-commons/LICENSE.txt > /jakarta-commons/build.properties.sample > /jakarta-commons/build.xml > /jakarta-commons/charter.html > /jakarta-commons/incl_nav.xml > /jakarta-commons/maven.xml > /jakarta-commons/navigation.vm > /jakarta-commons/project.xml One significant omission from this list is /jakarta-commons/combo/. Any discussion of centralising global build and site creation needs to take this into account as well. > > 1.) I'm suggesting the following changes initially for Maven related stuff: > > /jakarta-commons/commons-site/xdocs > /jakarta-commons/commons-site/project.xml > /jakarta-commons/commons-site/navigation.vm > /jakarta-commons/commons-site/maven.xml > /jakarta-commons/commons-site/incl_nav.xml > /jakarta-commons/commons-site/LICENSE.txt I don't like commons-site (or site either) because it's more than just the web site. I'd be more tempted to call it something like shared-build. Note that any changes here need to preserve the ability to build components using 'ant clean dist', regardless of whether the component has been Mavenised, so that they don't break the nightly build process. -- Martin Cooper > > --- > > This change would require the project.xml's for each project in both the > jakarta-commons and jakarta-commons-sandbox to have its extends tag > adjusted and any relative references to "commons-site" files adjusted. > > This change will be done within the cvs directory of the server to > maintain historical info on the changes to these files. > > -Mark > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org