Return-Path: Delivered-To: apmail-avalon-dev-archive@www.apache.org Received: (qmail 59655 invoked from network); 7 Nov 2003 02:42:07 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Nov 2003 02:42:07 -0000 Received: (qmail 17245 invoked by uid 500); 7 Nov 2003 02:41:48 -0000 Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 17183 invoked by uid 500); 7 Nov 2003 02:41:47 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 17152 invoked from network); 7 Nov 2003 02:41:47 -0000 Received: from unknown (HELO imf25aec.mail.bellsouth.net) (205.152.59.73) by daedalus.apache.org with SMTP; 7 Nov 2003 02:41:47 -0000 Received: from mail.bellsouth.net ([205.152.59.159]) by imf25aec.mail.bellsouth.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with SMTP id <20031107024156.VQOT1843.imf25aec.mail.bellsouth.net@mail.bellsouth.net>; Thu, 6 Nov 2003 21:41:56 -0500 X-Mailer: Openwave WebEngine, version 2.8.11 (webedge20-101-194-20030622) From: To: CC: , Subject: Merging repository discussions Date: Thu, 6 Nov 2003 21:41:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20031107024156.VQOT1843.imf25aec.mail.bellsouth.net@mail.bellsouth.net> 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 Hi Jason, > Just a note to any Maven developers who are interested in discussing the > format of the future repository layout for Apache are welcome to join in > at repository@apache.org. I think we have lots to offer in this area so > if you have some pop into the discussions. Very cool you have good timing. Have you had a chance to look at some of the discussions on the avalon-dev list regarding an API for building repository aware Avalon applications. It would be nice to merge our discussions and these topics together as one community rather than fragmenting it. For starters here are links to some of those related threads: http://nagoya.apache.org/eyebrowse/ReadMsg?listName=dev@avalon.apache.org&msgNo=22035 http://nagoya.apache.org/eyebrowse/ReadMsg?listName=dev@avalon.apache.org&msgNo=22038 I separated it into two parts as two trails to track each peice separately. I may have gotten too creative here ;-). Basically we're shooting for having a means to associate attributes with artifacts within the repository and have a generic API for repository aware and/or repository bootstrapping applications. The ideas being discussed revolve around the notion of an attribute database to be used to centrally manage project related artifact attributes. This way the repository becomes a queriable artifact directory as well as a artifact store. Are these ideas appealing to the Maven community? What can we do to consolidate our efforts? Sincerely, Alex Karasulu --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org