Return-Path: 
 <m2-dev-return-189-apmail-maven-m2-dev-archive=maven.apache.org@maven.apache.org>
Delivered-To: apmail-maven-m2-dev-archive@www.apache.org
Received: (qmail 20014 invoked from network); 16 Jun 2004 04:48:00 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 16 Jun 2004 04:48:00 -0000
Received: (qmail 63841 invoked by uid 500); 16 Jun 2004 04:48:29 -0000
Delivered-To: apmail-maven-m2-dev-archive@maven.apache.org
Received: (qmail 63791 invoked by uid 500); 16 Jun 2004 04:48:28 -0000
Mailing-List: contact m2-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:m2-dev-help@maven.apache.org>
list-unsubscribe: <mailto:m2-dev-unsubscribe@maven.apache.org>
list-post: <mailto:m2-dev@maven.apache.org>
List-Id: "Maven 2 Developers List" <m2-dev.maven.apache.org>
Reply-To: "Maven 2 Developers List" <m2-dev@maven.apache.org>
Delivered-To: mailing list m2-dev@maven.apache.org
Received: (qmail 63772 invoked by uid 99); 16 Jun 2004 04:48:28 -0000
Received: from [203.197.93.226] (HELO VMA) (203.197.93.226)
  by apache.org (qpsmtpd/0.27.1) with SMTP; Tue, 15 Jun 2004 21:48:28 -0700
From: "Vincent Massol" <vmassol@pivolis.com>
To: "'Maven 2 Developers List'" <m2-dev@maven.apache.org>
Subject: RE: artifact types/extensions
Date: Wed, 16 Jun 2004 10:29:39 +0530
Organization: Pivolis
Message-ID: <042501c4535e$bac39e70$64eafb0a@vma>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
In-Reply-To: <1087350131.40cfa573f2275@postoffice.tpg.com.au>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Hi Brett,

I agree that we need a way to relate different produced artifacts to a
project id. ATM this is not possible and causing problems for the ejb
plugin for example (which generates 2 artifacts: a main jar + a client
jar).

A "derivative" would work I guess. 

I'd much prefer that the version remains at the end of the artifact name
though.

What is the "format"? Is it the extension?

It is currently not possible to introduce a new artifact type that
doesn't end with .<type> (like we need for ear, war, rar, etc) without
modifying Maven core code. Adding the optional <extension> (or <format>)
element would allow for this.

Thanks
-Vincent

> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: 16 June 2004 07:12
> To: Maven 2 Developers List
> Subject: artifact types/extensions
> 
> Hi,
> 
> I'm just checking how this sits in m2 land so the stuff I'm hacking
into
> m1's
> artifact is somewhat compatible.
> 
> So, we have single projects generating multiple artifacts of different
> types
> (dists, jars, documentation, poms, etc). In m1, there is a mapping of
type
> to
> extension, so one type = one extension.
> 
> I believe this is taken care of so that there can be multiple
different
> extensions for a single type (where the artifact is the same, but
> presented
> differently - eg tar.gz vs zip, etc) - is this correct?
> 
> What about src dists vs bin dists? I originally thought of them as
> different
> types, but this isn't really the same thing. Also - you really want to
> name the
> files differently. This also applies to things like ejb where you have
a
> client JAR.
> 
> What I was thinking was that there is also a "derivative" attribute of
an
> artifact, that goes between version and extension. What do people
think?
> 
> So the final specification of an identifier for an artifact would be:
> groupId
> artifactId
> version
> type
> derivative
> format
> 
> Where derivative defaults to none and each type has one default
format,
> although
> formats are not related to type explicitly. The filename would be:
> groupId/types/artifactId-version-derivative.format
> Where -derivative is optional and version may be replaced by a
snapshot
> version.
> 
> Thoughts?
> 
> - Brett