Return-Path: 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 5C2E1E32F for ; Fri, 8 Mar 2013 08:54:55 +0000 (UTC) Received: (qmail 89953 invoked by uid 500); 8 Mar 2013 08:54:53 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 89772 invoked by uid 500); 8 Mar 2013 08:54:52 -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 89763 invoked by uid 99); 8 Mar 2013 08:54:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Mar 2013 08:54:52 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of willem.voogd@dayon.nl designates 209.85.215.179 as permitted sender) Received: from [209.85.215.179] (HELO mail-ea0-f179.google.com) (209.85.215.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Mar 2013 08:54:46 +0000 Received: by mail-ea0-f179.google.com with SMTP id f15so80651eak.10 for ; Fri, 08 Mar 2013 00:54:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dayon.nl; s=dkim; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zDivPVnR4kzgLPYcnAsVuygfB5X9njhRcc7QtLMuYEQ=; b=iEWdjLlOZF+80W09Hz78mGfscohVBCb6+3dJBoUwxSvrRHTpNBwTHaPETC2cIa4Esx cFYJzJiaTV1E70vhvJQVoiBsP9W6KrhuE6enxEG35kY2z30TDMxAOo/kkSrnKjLvIyvt upaEl+mbwLMqM5MMDH0bgaHrUgpfZ2sOiIzJQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=zDivPVnR4kzgLPYcnAsVuygfB5X9njhRcc7QtLMuYEQ=; b=XRNF2eDEWWa45Nlp5XqYviQtN6r8nHnunlp9Y5w5qIzAkPLILcH8ioEh0oFRYQV5rB 2Jic02WE5ZQlgCmXz8AgxaefGaayFGI724geV7SZFvT0mon5zYULHNkOzN81PCSj/rdP U2dh3+QRaOjzTcPD/yi4yRykXHA3RG0OX8IAF1PXuxIPAODkx5XYCruNWgp79eTy+fWE wU0APuF5rNtj3MMagU2P1dAfS6bmmsWRkfeaS1L7wUrpiK5T5gFPcAlKpHLqABcyobBS 2agqmgpkw7KlMw3kqQz05exBpug99cF0aGkHccnubwJzT1NbtqW3qPG3MR6l6yOIoZ2l MPfw== X-Received: by 10.14.4.69 with SMTP id 45mr3383048eei.0.1362732865136; Fri, 08 Mar 2013 00:54:25 -0800 (PST) Received: from [192.168.100.22] (82-197-206-32.dsl.cambrium.nl. [82.197.206.32]) by mx.google.com with ESMTPS id a1sm6480261eep.2.2013.03.08.00.54.23 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Mar 2013 00:54:24 -0800 (PST) Message-ID: <5139A73E.4020104@dayon.nl> Date: Fri, 08 Mar 2013 09:54:22 +0100 From: Willem Voogd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3 MIME-Version: 1.0 To: Maven Users List Subject: Re: git release:prepare does not commit the poms (Linux) References: <51389041.5090301@dayon.nl> <5138E401.3090107@talios.com> In-Reply-To: <5138E401.3090107@talios.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQl6Ri+8dDRSVT8sfgenkszbcWPoA2Fzn01B1RGN4nOW9Dt6Dgwbr+1g3Fqi8js73jIaXZ/6 X-Virus-Checked: Checked by ClamAV on apache.org BTW With 2.4 the tag *is* set remote as well, according to my milage... Op 07-03-13 20:01, Mark Derricutt schreef: > The 2.4 git problems are related to the release plugin ignoring local > checkout/disabling push settings primarily, so that your release is > tagged locally, but then MRP tries to clone the tag from upstream and > fails. > > Either way, dropping back to 2.3.2 to eliminate those issues would be > a good point of call. > > One thing I've also noticed that sounds familiar, make sure you don't > have a release.properties in your working directory prior to a new > release - sometimes I've noticed it gets left behind somehow and > depending on whats in that file, MRP will "resume the release" from a > point where it thinks your version number has already been updated - > and thus releases/deploys a -SNAPSHOT to your release repo. > > Mark > > > Robert Scholte wrote: >> could you try to use maven-release-plugin 2.3.2? >> There are some known issues with GIT and the maven-release-plugin >> 2.4, which need to be fixed in the SCM project first. > > --------------------------------------------------------------------- > 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