From depot-dev-return-865-apmail-incubator-depot-dev-archive=incubator.apache.org@incubator.apache.org Thu Aug 19 19:28:37 2004 Return-Path: Delivered-To: apmail-incubator-depot-dev-archive@www.apache.org Received: (qmail 89139 invoked from network); 19 Aug 2004 19:28:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Aug 2004 19:28:37 -0000 Received: (qmail 61789 invoked by uid 500); 19 Aug 2004 19:28:35 -0000 Delivered-To: apmail-incubator-depot-dev-archive@incubator.apache.org Received: (qmail 61713 invoked by uid 500); 19 Aug 2004 19:28:33 -0000 Mailing-List: contact depot-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: "Depot Development" List-Id: Depot Development Delivered-To: mailing list depot-dev@incubator.apache.org Received: (qmail 61673 invoked by uid 99); 19 Aug 2004 19:28:33 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [202.187.40.2] (HELO f2.hedhman.org) (202.187.40.2) by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 19 Aug 2004 12:28:30 -0700 Received: from f2.hedhman.org (f2.hedhman.org [127.0.0.1]) by f2.hedhman.org (8.12.8/8.12.8) with ESMTP id i7JJSPnr021908; Fri, 20 Aug 2004 03:28:25 +0800 From: Niclas Hedhman Organization: Private To: "Avalon Developers List" Subject: Re: Management of "external" JARs et. al. Date: Fri, 20 Aug 2004 03:28:25 +0800 User-Agent: KMail/1.5 References: <200408191235.32313.tobias.wolf5@epost.de> In-Reply-To: <200408191235.32313.tobias.wolf5@epost.de> Cc: depot-dev@incubator.apache.org, dev@maven.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200408200328.25111.niclas@hedhman.org> X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Thursday 19 August 2004 18:35, Tobias Wolf wrote: > In an first approach I simply created the directory 'template' and 'jars' > under my .magic/main and defined it as an ressource in my index.xml. When i > can append it to the dependencies of my project and i am finished. Now I am > able to use the functionality provides with this JAR in my Servlets. > > Maybe there already exists an better way to do this and I missed it. There are other ways, but let's continue on the thread you started on IRC. There are a few issues with 'external non-mavenized artifacts'; 1. How are they included into a project managed by Magic? 2. How do we assign groups and possibly name and version to these? 3. And MOST IMPORTANTLY, how do ensure that all users, across both Magic and Maven (possibly others) are assigning the same group? Tobias made the contribution of raising the issue on IRC, and I have some ideas. Let's just drop the first 2 and concentrate on what really matters... If we can get to an agreement with Maven folks, that a LINK document can exist in the central repositories, and that LINKDOC contains information to the user where/how to download the jar file, and perhaps a "Naming Rule" in form of a regular substitution expression, we could actually get somewhere. That would allow "us" (as in people who are interested in the central repository concept) to provide the proper grouping and how the versioning is handled of the downloaded artifact. The tools maker are then free to figure out how to communicate this information to the user. WDYAT ?? Cheers Niclas -- +------//-------------------+ / http://www.bali.ac / / http://niclas.hedhman.org / +------//-------------------+