Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 47456 invoked from network); 2 Feb 2011 22:26:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Feb 2011 22:26:29 -0000 Received: (qmail 37144 invoked by uid 500); 2 Feb 2011 22:26:26 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 37040 invoked by uid 500); 2 Feb 2011 22:26: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 37028 invoked by uid 99); 2 Feb 2011 22:26:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Feb 2011 22:26:26 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kalle.o.korhonen@gmail.com designates 209.85.214.43 as permitted sender) Received: from [209.85.214.43] (HELO mail-bw0-f43.google.com) (209.85.214.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Feb 2011 22:26:19 +0000 Received: by bwz14 with SMTP id 14so1152198bwz.30 for ; Wed, 02 Feb 2011 14:25:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=LVcufon0D1p4rNjCT97ywce2Cj3PmNTq6zGJIgns/DU=; b=c7H9mA9XM4uArEFKC4VIUcgzJBq2fdIh+StmB9sh2PzdH7URllCfCvhGaDWBtG/aYY Gd8tb9aPyLYTxtTHOf+8rJwkf3VSX/Iq186RJBRssUg7S3YEIvySTEetXqeVr6kKCaY8 tt+TqxyIoQJ/gwLWKvR0JP1Jwb39kt74kpqvU= 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:content-transfer-encoding; b=jcV8vfB94h6PQA2HDDrJR7QrkJV0GyR+uWvWAEBmRiD2QZf6txJwp3MVN1b6ePdZrx uyXIhSE/k8IK7FahhEAQ1QSvs6vb40vUD+nnoW/1Kvjdb1yz4JpqPOIPBL+ByzjTt/OH 96BnQGhZ9/AS28i1/sOacfsU2wD/D8Vt6G28Y= MIME-Version: 1.0 Received: by 10.204.117.77 with SMTP id p13mr8979837bkq.19.1296685558080; Wed, 02 Feb 2011 14:25:58 -0800 (PST) Received: by 10.204.75.203 with HTTP; Wed, 2 Feb 2011 14:25:58 -0800 (PST) In-Reply-To: References: Date: Wed, 2 Feb 2011 14:25:58 -0800 Message-ID: Subject: Re: Local Clone Helpfullness as a possible Maven Plugin From: Kalle Korhonen To: Maven Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Why do you need to re-release? I typically checkout/clone, build, edit the pom directly and change the version to --1, then take both the pom and the (snapshot) library and deploy them to Nexus. Kalle On Wed, Feb 2, 2011 at 2:17 PM, Benson Margulies wr= ote: > Here's something that happens to me frequently. > > Goal: make a local release off the trunk of some FOSS thing that will > be a while releasing a fix that I need. > > Typical set of activities: > > 1: git svn clone > 2: =A0branch > 3: edit poms, change version, scm paths, deploymentRepository > 4: run release plugin > > #3 is rather a fiddly, error prone process. > > If, on top of this, I also want to make local changes and push them > back, it's fiddly to sort out the purely local pom changes. > > All of this suggests two possible lines of country: > > 1) more fun in the version plugin to deal with scm and deployment. > > 2) some sort of a way to 'shadow' a POM with local changes instead of > editing them in. > > Opinions? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > For additional commands, e-mail: users-help@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org