Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (herse.apache.org: domain of mcculls@gmail.com designates
 64.233.184.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=ZIL2F9LRMX5FpVdTiyThcn08cZdi0bzVD0r9aPNPHBqlSYjGNU2IsMjR0YuIEaJgFC1tqbgjpDVinBcrNFoa2FyMcxhKjgfJeTYooX7dZGhOnf+U2KTxyJ08HHPusT+qBPpE+dPSK2d7mJTSC3EYa86FNDVB1L1QtGigmqQlUXA=
Message-ID: <81f0d9c0705220859s52f3bdc6ld54028cbe4579443@mail.gmail.com>
Date: Tue, 22 May 2007 23:59:53 +0800
From: "Stuart McCulloch" <stuart.mcculloch@jayway.net>
Sender: mcculls@gmail.com
To: dev@felix.apache.org
Subject: Re: Roadmap
In-Reply-To: <4651E897.5080603@ungoverned.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <487a994c0705201211gaa8f51bmfd818c96947c2996@mail.gmail.com>
	 <4650D062.2090905@ungoverned.org> <46518275.7050202@verizon.net>
	 <465199DB.5040804@ungoverned.org>
	 <1a5b6c410705210844h3f093ec2vcf8aef0d94493ca4@mail.gmail.com>
	 <4651C7EC.70907@ungoverned.org>
	 <1a5b6c410705211000k5810336cy757dcc65138a7fa4@mail.gmail.com>
	 <4651E122.9030903@ungoverned.org>
	 <1a5b6c410705211129u78b00c9fq670693423ef98f93@mail.gmail.com>
	 <4651E897.5080603@ungoverned.org>

On 22/05/07, Richard S. Hall <heavy@ungoverned.org> wrote:
> In summary, the dilemma we had was that everyone wanted the artifactId
> to be the short name and the JAR file to be the long name. But if we
> made the artifactId the short name, then we also got the short name for
> the JAR.

FYI, it is possible to alter the final name of the jarfile from the default.

The maven super pom, which all top-level poms inherit from, defines:

  <build>
    <finalName>${artifactId}-${version}</finalName>
    ... etc ...

but afaik there's no reason why the top-level felix pom couldn't say:

  <build>
    <finalName>${groupId}.${artifactId}-${version}</finalName>
    ... etc ...

then any jars in target folders would have the long form of the name.

However, the jarfile installed in the maven repository will still have
the standard ${artifactId}-${version} name, because that's defined
by the repository layout.

-- 
Cheers, Stuart