Return-Path: 
 <users-return-126285-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-users-archive@www.apache.org
Delivered-To: apmail-maven-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BB2B99533
	for <apmail-maven-users-archive@www.apache.org>;
 Fri, 16 Mar 2012 20:52:10 +0000 (UTC)
Received: (qmail 36542 invoked by uid 500); 16 Mar 2012 20:52:08 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 36452 invoked by uid 500); 16 Mar 2012 20:52:08 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 36444 invoked by uid 99); 16 Mar 2012 20:52:08 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2012 20:52:08 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of maven.2.user@gmail.com
 designates 209.85.213.43 as permitted sender)
Received: from [209.85.213.43] (HELO mail-yw0-f43.google.com) (209.85.213.43)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2012 20:52:03 +0000
Received: by yhkk6 with SMTP id k6so5684226yhk.30
        for <users@maven.apache.org>; Fri, 16 Mar 2012 13:51:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=ROQl/WNcSTcYcov8kMyHlk+tTPv85hdqLyuz9q1YHR8=;
        b=vNXInE7jugLXZ3deDFOvjqf7sQViud71ih6satkAoDasniCJjwmp7513weW8+pVGN2
         YmBHyFCsboAR18RSaXdfrISA3LD5mFG+4kvU9fIcijY+3e2OiGM4UsE7bvMBxcstaZVo
         yDWC/FrsTFor3nISEGeXCpSgnyaxPMiyrYjk1GT3lfe+8khZO4UmeBG/VwtY+Q3ejgbv
         ErErzVtb5m2Ph/Wz3icDPU4qOzQ/wmnmRGU9Kbyp/Hn79uWzAQdZa4/HHl/ZGrDGW1u1
         D2LoV1QAlxOtB0LtjXM9RGJ2fgSKjp/t29gt10vIV16swt+cWp35RvIMdKIhdB9aKmRy
         TM2w==
MIME-Version: 1.0
Received: by 10.60.29.39 with SMTP id g7mr4731792oeh.6.1331931102948; Fri, 16
 Mar 2012 13:51:42 -0700 (PDT)
Received: by 10.182.2.163 with HTTP; Fri, 16 Mar 2012 13:51:42 -0700 (PDT)
In-Reply-To: 
 <CAChPNbejw1F02+TiO9AO3ejZUGm0Jud=vkRjFZcuMp0LNSMSPQ@mail.gmail.com>
References: 
 <CAChPNbcp_JBhwiPGnHDVAxEw13Q93FCkQ3+uMP1v45URcjaO_A@mail.gmail.com>
	<jk015a$1i1$1@dough.gmane.org>
	<CAChPNbfXvEhviPNfAQ3TOr8=2EDQ2HOoNjXLV2j920EzSS=uyA@mail.gmail.com>
	<440D69AA5A6A81428BD620AEA5AC918118A73C1338@MX33A.corp.emc.com>
	<CAChPNbejw1F02+TiO9AO3ejZUGm0Jud=vkRjFZcuMp0LNSMSPQ@mail.gmail.com>
Date: Fri, 16 Mar 2012 16:51:42 -0400
Message-ID: 
 <CAChPNbfPbjNhr3jSdM2Jnp1tDQJAHjx4wSA532maxktVL+qAZA@mail.gmail.com>
Subject: Re: Attach a random file to the deploy process
From: Maven User <maven.2.user@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=e89a8ff2563241ad0604bb6260a5
X-Virus-Checked: Checked by ClamAV on apache.org

--e89a8ff2563241ad0604bb6260a5
Content-Type: text/plain; charset=ISO-8859-1

Ok, now getting a bit pissed.

Maven deploy:deploy-file is NOT liking my url to my snapshot repository.

Is there some magic or can I just use -Durl=http://<server>/<path>/snapshots

On Fri, Mar 16, 2012 at 4:10 PM, Maven User <maven.2.user@gmail.com> wrote:

> Preaching to the choir my friend.
>
> I tried hacking up the build helper plugin as suggested above, but the
> ArtifactId (understandably) can't be changed.
>
> Thanks all!
>
>
> On Fri, Mar 16, 2012 at 3:57 PM, <Chad.Davis@emc.com> wrote:
>
>>
>>
>> > Well, kinda - that only allows you to adjust extension and classifier.
>> >
>> > I _know_, we're swimming up stream here a bit.
>> >
>> > I'm pulling down the code for the buildhelper - I'd like to be able to
>> control
>> > final name or artifactId at least :-/
>>
>> I would suggest that controlling the name of the artifact is flagrant
>> violation of the maven way.  I just did a bunch of this work and
>> I used the classifier to clearly identify the purpose of the attached
>> artifact.  Assuming your .doc file was something like "release notes", you
>> could use a classifier of "releaseNotes".  I assume your desire to use a
>> different name comes from other elements of your ecosystem wanting/ needing
>> a different name . . . ?  I suggest changing those things if possible.
>>
>> If they really have to be named something else, perhaps they should be
>> attached to another project with that name.  Or even deployed ad hoc via
>> the deploy:deploy-file mojo?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>

--e89a8ff2563241ad0604bb6260a5--