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 D1A91100DA for ; Sat, 9 Nov 2013 13:31:57 +0000 (UTC) Received: (qmail 87103 invoked by uid 500); 9 Nov 2013 13:31:51 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 86674 invoked by uid 500); 9 Nov 2013 13:31:50 -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 86666 invoked by uid 99); 9 Nov 2013 13:31:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Nov 2013 13:31:48 +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 (nike.apache.org: domain of gordon.cody@zafin.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bk0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Nov 2013 13:31:42 +0000 Received: by mail-bk0-f48.google.com with SMTP id u10so1134244bkz.35 for ; Sat, 09 Nov 2013 05:31:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=YxNjWsMu0fxBXobQvYkSHZ8+TmzpvYTK/48LipC3Np4=; b=ZVVr772GK2PuYroBLNci2oj/KtRu0HUiZH60oZ4szzFsecJhUoKgXUmwjxcWMAB2Ns izcEZZetvukzhlKU2s3VGdUYokvCESKS3lDmU4D+mKEvhQigEnbNMd0DNOrVMlbJpyfk mKSCiIeTLIN+W5jblZjRJgPsag8L/Q9QEl3qiCmtfXMqCGp2LsWUi3OHUURFAo+JQzMy Qou98bRBLsb3G3EKNVbU9p8WLr1Vf6TzHYtTPwK7zQMMCOFoGeJccIC12zxBtqXqjdfl I0Vr4u5bEVHFrmSZweK8/qJ1z8HHNcjcKGA/IWglgIFnqZEynelXO0IUA1NYo+dZ4Qz6 6M8w== X-Gm-Message-State: ALoCoQn0+9qpn8HrqRR5iTgG/+NPXYC4ItBgE5sbyIlnDHMFU/nstAYNPwOqbQfP9rNT7zNCBOTU MIME-Version: 1.0 X-Received: by 10.204.121.201 with SMTP id i9mr14696075bkr.13.1384003881668; Sat, 09 Nov 2013 05:31:21 -0800 (PST) Received: by 10.204.171.14 with HTTP; Sat, 9 Nov 2013 05:31:21 -0800 (PST) In-Reply-To: <54D3CE24C875604ABE7E6722C0EB8854162EC9E238@QUIPSY1.Quipsy.local> References: <1CBE7B8B-FD7E-4F2F-9EAE-CD5D6ABDCF3F@gold-family.us> <54D3CE24C875604ABE7E6722C0EB8854162EC9E1CF@QUIPSY1.Quipsy.local> <54D3CE24C875604ABE7E6722C0EB8854162EC9E1DA@QUIPSY1.Quipsy.local> <54D3CE24C875604ABE7E6722C0EB8854162EC9E22A@QUIPSY1.Quipsy.local> <54D3CE24C875604ABE7E6722C0EB8854162EC9E238@QUIPSY1.Quipsy.local> Date: Sat, 9 Nov 2013 08:31:21 -0500 Message-ID: Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version From: Gordon Cody To: Maven Users List Content-Type: multipart/alternative; boundary=001a1133494ebc823f04eabe83bd X-Virus-Checked: Checked by ClamAV on apache.org --001a1133494ebc823f04eabe83bd Content-Type: text/plain; charset=ISO-8859-1 You may want to upgrade maven itself once more. It is not just maven itself but the combination of plugins that are used and your environment matters. Ensure that each maven goal you plan on using in your environment actually works in your environment before you need it for real. Maven has to work with your vcs, your artifact mgmt (nexus/artifactory/other), your network security policies, etc. all at the same time. When we began upgrading existing projects from mvn-2.0.9 we had to also upgrade numerous plugins. It took some effort to find the combination of plugins/configuration that allowed us to do 'mvn deploy' successfully with mvn-3.0.4. But 'mvn release' did not work in our environment until mvn-3.0.5 was released!!. Underlying plugin(s) had changed. Regards, Gord On Sat, Nov 9, 2013 at 4:55 AM, Markus Karg wrote: > Robert, > > no need to teach me about completeness of reports -- I am in the reverse > situation day by day as you can imagine. The problem was that I had the > problem since I migrated to Maven 3 from day one with even the smallest > possible POM (it looked 'obvious' to me) and did not have the idea there > might be a fix already already which is not contained in Maven 3 so far. In > fact this is why I would love to have the ability to use version ranges in > plugin dependencies! ;-) > > Anyways, as all is fixed now, thanks for the kind help! :-) > -Markus > > -----Original Message----- > From: Robert Scholte [mailto:rfscholte@apache.org] > Sent: Freitag, 8. November 2013 18:52 > To: Maven Users List > Subject: Re: AW: AW: AW: mvn release:prepare does not update parent version > > Op Fri, 08 Nov 2013 16:30:30 +0100 schreef Markus Karg : > > > I wonder why someone fixed it but didn't close > > https://jira.codehaus.org/browse/MRELEASE-837...! > > Well, is was probably already fixed for a long time. Since you only had a > description it will take some time to fix it, since it must first be > reproducible. That's why attaching a sample project helps, and a patch with > a possible fix even more. > > In this case it was the log-file which triggered me: first update the > version of the plugin and see if it has been already been fixed. > > It is all about being as complete as possible :) > > Robert > > --------------------------------------------------------------------- > 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 > > -- Best Regards, Gord Cody Release Manager Zafin Labs Americas Inc. 179 Colonnade Road-Suite 100, Ottawa ON, Canada Phone: +1 (613) 216-2504 Fax: +1 (613) 688-1374 Mobile: +1 613-601-2734 Web: http://zafin.com Email: gordon.cody@zafin.com --001a1133494ebc823f04eabe83bd--