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 EA2A910591 for ; Fri, 6 Dec 2013 23:15:17 +0000 (UTC) Received: (qmail 96321 invoked by uid 500); 6 Dec 2013 23:15:16 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 96248 invoked by uid 500); 6 Dec 2013 23:15:16 -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 96240 invoked by uid 99); 6 Dec 2013 23:15:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 23:15:15 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [24.37.79.202] (HELO smtp.artifact-software.com) (24.37.79.202) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 23:15:12 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.artifact-software.com (Postfix) with ESMTP id 5270E6A7A78 for ; Fri, 6 Dec 2013 18:14:51 -0500 (EST) X-Virus-Scanned: amavisd-new at artifact-software.com Received: from smtp.artifact-software.com ([127.0.0.1]) by localhost (smtp.artifact-software.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDBjDbxxXGRU for ; Fri, 6 Dec 2013 18:14:42 -0500 (EST) Received: from [192.168.3.170] (unknown [192.168.3.170]) by smtp.artifact-software.com (Postfix) with ESMTP id 048546A7A71 for ; Fri, 6 Dec 2013 18:14:42 -0500 (EST) Message-ID: <52A25A5F.3080608@artifact-software.com> Date: Fri, 06 Dec 2013 18:14:39 -0500 From: Ron Wheeler Reply-To: rwheeler@artifact-software.com Organization: Artifact Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: users@maven.apache.org Subject: Re: Version resolution question (was: plugin version ranges errors with Maven 3.1.1) References: <1B8FF9BB83FDCE44AB581D7E394AB90D2A3831FB@USSTLDAGBE1.corp.amdocs.com> In-Reply-To: <1B8FF9BB83FDCE44AB581D7E394AB90D2A3831FB@USSTLDAGBE1.corp.amdocs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org nexus * http://repo.....com:8081/nexus/content/groups/public This might help Ron On 06/12/2013 6:06 PM, John Dix wrote: > Thanks Curtis and everyone. > > I have a follow up question around the same thing build. > > The command line I am using: maven clean install > > Our 3.1.1 maven build is having issues finding the plugins in our .m2 directory unless I specify on the command line -Pmavencentral which is defined in our .m2/settings.xml as such: > > > mavencentral > > > mcentral > http://sd-repo-2.eng.qpass.net:8081/nexus/content/repositories/central > > true > > > false > > > > > > mcentral > http://sd-repo-2.eng.qpass.net:8081/nexus/content/repositories/central > > true > > > false > > > > > > Which is our proxy to the public internet mavencentral server. > > I have tried using the -o and -U switches at the command line when executing without the -Pmavencentral and I receive the following: > > [ERROR] Plugin org.apache.maven.plugins:maven-shade-plugin:2.1 or one of its dependencies could not be resolved: Cannot > access qpass-nexus-hosted-releases (http://pd-repo2.eng.qpass.net:8081/nexus/content/repositories/releases) in offline > mode and the artifact org.apache.maven.plugins:maven-shade-plugin:jar:2.1 has not been downloaded from it before. -> [Help 1] > > I want it to look only in the .m2 repository. Is there another -D setting I need to speciy? Is there some place I should be looking to see for conflicting settings? > > -----Original Message----- > From: ctrueden.wisc@gmail.com [mailto:ctrueden.wisc@gmail.com] On Behalf Of Curtis Rueden > Sent: Friday, December 06, 2013 2:34 PM > To: Maven Users List > Subject: Re: plugin version ranges errors with Maven 3.1.1 > > Hi John, > > You might be able to use profiles to define a different version of maven-shade-plugin depending on the version of Maven being used. However, some caveats: > > 1) There is no explicit profile activation for Maven version. The hack people use is to activate based on the existence of a property known only to e.g. Maven 3.x. I am not sure what a good property would be for Maven > 3.1 specifically (i.e., not known to 3.0.x), but one probably exists. > > 2) When it comes to profiles, as Stephen Connolly likes to say: "that way madness lies." This hack will get your build done for you, but it is a hack, and you should never forget that it is a hack. Or to put another way: > it's technical debt. When the debt must be paid is unclear, but e.g. if the maven-shade-plugin produces a different binary result depending on which version you use, then you may run into apparently bizarre problems with users who built using Maven 3.1.1 rather than an older version, or vice versa, and it may take you some time to diagnose *why* it's happening > (surprise: it's because a different version of maven-shade-plugin got selected!), and so on. > > Such problems are why the other posters in this thread are encouraging you to just choose a version of maven-shade-plugin that works for you. You > *can* put into your POM that it requires a certain minimum Maven version [1], and Maven will (IIRC) just fail fast if the version is too old. That is a lot less mysterious than some subtle inconsistency in shaded artifact build results. And you'll get truly repeatable builds which are one of the fabulous benefits of a well-structured build system. > > Regards, > Curtis > > [1] http://maven.apache.org/pom.html#Prerequisites > > > On Fri, Dec 6, 2013 at 4:20 PM, John Dix wrote: > >> We are getting build failures when using 3.1.1 and the 2.0 shade plugin. >> It seems to be a documented issue: >> >> https://issues.apache.org/jira/browse/STANBOL-1212 >> >> So I wanted to be able to have the same parent pom for our builds that >> still require 3.0.5 which currently sets it to 2.0 and does not run >> into this error. >> >> -----Original Message----- >> From: Wayne Fay [mailto:waynefay@gmail.com] >> Sent: Friday, December 06, 2013 12:51 PM >> To: Maven Users List >> Subject: Re: plugin version ranges errors with Maven 3.1.1 >> >>> Agreed however I need to support two builds in our environment one >>> that uses Maven 3.0.5 and one that does 3.1.1 without having to >>> change >> the file every time. >> >> Sorry for asking the obvious question, but what prevents you from >> specifying version [2.0] or whatever and using that with both 3.0.5 >> and 3.1.1? Is there some incompatibility I am unaware of presently? >> >> Wayne >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org >> For additional commands, e-mail: users-help@maven.apache.org >> >> >> This message and the information contained herein is proprietary and >> confidential and subject to the Amdocs policy statement, you may >> review at http://www.amdocs.com/email_disclaimer.asp >> > This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, > you may review at http://www.amdocs.com/email_disclaimer.asp > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org > For additional commands, e-mail: users-help@maven.apache.org > > -- Ron Wheeler President Artifact Software Inc email: rwheeler@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org