Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 62367 invoked from network); 4 May 2009 17:11:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 May 2009 17:11:29 -0000 Received: (qmail 15206 invoked by uid 500); 4 May 2009 17:11:26 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 15100 invoked by uid 500); 4 May 2009 17:11:26 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 15090 invoked by uid 99); 4 May 2009 17:11:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 17:11:26 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of geoffrey.wiseman@gmail.com designates 209.85.218.219 as permitted sender) Received: from [209.85.218.219] (HELO mail-bw0-f219.google.com) (209.85.218.219) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 17:11:16 +0000 Received: by bwz19 with SMTP id 19so5113053bwz.12 for ; Mon, 04 May 2009 10:10:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=lGj/efk7SKHlhkORGKcFdoLnoN3Jur9kIuFvWpUfiyA=; b=DesiGshDU7C/lYrn6gqFlr6f+QewQotrVmiF89HwfHP5IakhC8jkRckmowxbHciTLe CvUHxLmVsfMg1uvlTEcvDhyz6CrdavUs6STW3Nvg4w86rjlYS4oo8gDC6j8GxNe8D9mc CWyQ5K292+KWSk21IayR7CS77wOy2zNpkqcwA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=st5D2QgJ1CyBshODojc+IeA9mIvU1r3CYlxL/mzd3mD0teYCMKXkgUBeKwgl84tWwO HSsu6GygJgro3qEVP2y8NSRm7p3qU4+x/GpIRxcsuok5H6EuvDIofAWbzrhb0AaBTUvO HrCK3SAlAaURGzJnrAB0NxSH7XE++vzjWy4pE= MIME-Version: 1.0 Received: by 10.223.107.198 with SMTP id c6mr2436593fap.32.1241457054799; Mon, 04 May 2009 10:10:54 -0700 (PDT) In-Reply-To: <3a15f5ad0905041001l4722f08fhdeb397b773043ae9@mail.gmail.com> References: <23371539.post@talk.nabble.com> <3a15f5ad0905041001l4722f08fhdeb397b773043ae9@mail.gmail.com> Date: Mon, 4 May 2009 13:10:54 -0400 Message-ID: <835d522e0905041010p7bb20f2cs7d318fe96ce50781@mail.gmail.com> Subject: Re: Managing Modified Dependencies From: Geoffrey Wiseman To: Maven Users List Content-Type: multipart/alternative; boundary=001636c5b0eec15a110469193ec7 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5b0eec15a110469193ec7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Mon, May 4, 2009 at 1:01 PM, Nick Stolwijk wrote: > 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. If 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. - Geoffrey -- Geoffrey Wiseman http://www.geoffreywiseman.ca/ --001636c5b0eec15a110469193ec7--