Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of anders.g.hammar@gmail.com
 designates 209.85.219.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=MruSjxT1R1WDrzsKBfAuKrZtOz6MpzE6/9wv4pj4uwPLqgctrcwb5tuKD4rGHtYJtZ
         1kS6D2xN3XaJXOTwx+BnG6GWUqrzEr1vuSZEkhpiEn39fMv2XhJXoTfuPlIUKfsLeiKw
         5BcVyv8990dbEH61NMJtInkjZMfZd4r+w39KA=
MIME-Version: 1.0
Sender: anders.g.hammar@gmail.com
In-Reply-To: <835d522e0905041010p7bb20f2cs7d318fe96ce50781@mail.gmail.com>
References: <23371539.post@talk.nabble.com>
	 <3a15f5ad0905041001l4722f08fhdeb397b773043ae9@mail.gmail.com>
	 <835d522e0905041010p7bb20f2cs7d318fe96ce50781@mail.gmail.com>
Date: Mon, 4 May 2009 22:17:33 +0200
Message-ID: <fabd12810905041317v5f104698i30e382949737613b@mail.gmail.com>
Subject: Re: Managing Modified Dependencies
From: Anders Hammar <anders@hammar.net>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

As the initial scenario doesn't mention it, I would like to stress the
step of submitting the patch to the owner. This should as least make
it feasible to get fixed quickly at the source.

In any case, the two important things I think are to keep the original
groupId and artifactId (which was NOT the recommended way some time
ago), and also to define dependency versions through
dependencyManagament (so that there is just one place to change).

/Anders

On Mon, May 4, 2009 at 19:10, Geoffrey Wiseman
<geoffrey.wiseman@gmail.com> wrote:
> On Mon, May 4, 2009 at 1:01 PM, Nick Stolwijk <nick.stolwijk@gmail.com>wr=
ote:
>
>> Normally I just check out the source, apply my patches, update the
>> deploymentManament section to point to our inhouse repository, update
>> the version to x.y.z-companyname-1 and do a maven deploy. Then update
>> the documentation to mention which revision you checked out
>> (preferably a tag) and for which issues you have applied a patch, so
>> that the build is reproducible.
>>
>
> That'd would be roughly similar to how I would typically handle it. =A0If=
 the
> changes are significant, I might also check in to local source control.
>
> In all scenarios, I'd be hoping to get back on a public version ASAP.
>
> =A0- Geoffrey
> --
> Geoffrey Wiseman
> http://www.geoffreywiseman.ca/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org