Return-Path: 
 <users-return-132278-apmail-maven-users-archive=maven.apache.org@maven.apache.org>
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 5485610A0D
	for <apmail-maven-users-archive@www.apache.org>;
 Wed,  1 May 2013 15:31:19 +0000 (UTC)
Received: (qmail 92599 invoked by uid 500); 1 May 2013 15:31:17 -0000
Delivered-To: apmail-maven-users-archive@maven.apache.org
Received: (qmail 92511 invoked by uid 500); 1 May 2013 15:31:17 -0000
Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:users-unsubscribe@maven.apache.org>
List-Help: <mailto:users-help@maven.apache.org>
List-Post: <mailto:users@maven.apache.org>
List-Id: "Maven Users List" <users.maven.apache.org>
Reply-To: "Maven Users List" <users@maven.apache.org>
Delivered-To: mailing list users@maven.apache.org
Received: (qmail 92498 invoked by uid 99); 1 May 2013 15:31:17 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 15:31:17 +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 (athena.apache.org: domain of
 ansgar.konermann@googlemail.com designates 209.85.217.174 as permitted
 sender)
Received: from [209.85.217.174] (HELO mail-lb0-f174.google.com)
 (209.85.217.174)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 15:31:13 +0000
Received: by mail-lb0-f174.google.com with SMTP id t11so1559554lbd.19
        for <users@maven.apache.org>; Wed, 01 May 2013 08:30:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:content-type;
        bh=oIYG0Ks+8D+Lkta90TRFhfp+i4BTSEzp8DlvTrc3Lbs=;
        b=tm5hAODFGW3WzNiV5rdQ0LBPo9lCuFm9I335yfBtqLa5rQthSQIb2C7FuNF1BdDk1T
         7i/6SBc2XBpPugGw/krIic5m5cmZc7e9gek3kpshJ6JGlcfGfjO7fsIIJ3iQeTibOYED
         qWwzMO5E30KI653qt8EM7X8eliSAUvU1o5lBgcgczsjNcyu9yV9VFW5/HBAKdwXKIplC
         uJ+jqSasEHUV5lLESkixZX9cmOzo0PwMICHXYdhTA8KrFleqWC+H+GaEg6G2286+TPSi
         ngN/Ws6miDjJz9v0XhZom860dw8nMIKRcLMZQOGefYwK1j8m25Hc9wbs5owXKHUrKyks
         acqw==
MIME-Version: 1.0
X-Received: by 10.112.140.33 with SMTP id rd1mr1321724lbb.44.1367422251748;
 Wed, 01 May 2013 08:30:51 -0700 (PDT)
Received: by 10.114.27.68 with HTTP; Wed, 1 May 2013 08:30:51 -0700 (PDT)
Received: by 10.114.27.68 with HTTP; Wed, 1 May 2013 08:30:51 -0700 (PDT)
In-Reply-To: <1367421251596-5754681.post@n5.nabble.com>
References: <1367421251596-5754681.post@n5.nabble.com>
Date: Wed, 1 May 2013 17:30:51 +0200
Message-ID: 
 <CA+U2j0odxMCb9pzQ8fWsBmUW0e-orpiVvr7vVOonrfnjie272A@mail.gmail.com>
Subject: Re: Another Maven 1 to 2 upgrade issue.
From: Ansgar Konermann <ansgar.konermann@googlemail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: multipart/alternative; boundary=001a11c38a3e92d44c04dba9cda1
X-Virus-Checked: Checked by ClamAV on apache.org

--001a11c38a3e92d44c04dba9cda1
Content-Type: text/plain; charset=ISO-8859-1

Make all the dependencies of the supporting jar <scope>provided</scope>

Ensure your app brings these dependencies and all *theirj transitive ones
in the "correct" version.

"provided" basically cuts off transitive dependencies.
Am 01.05.2013 17:15 schrieb "tedhohio" <tedhohio@gmail.com>:

> I 'inherited' responsibility for an application that has several jars
> compiled in Maven 1.  The main application itself is using Maven 2.  While
> I
> want to upgrade everything, my client hasn't yet given me time to do that
> sort of work between minor fixes and adding capability - I know, a common
> complaint.
>
> So I upgraded one of the supporting jars to Maven 2 and it seemed to work
> OK, until I integrated it into the main app.  Suddenly the main app is
> using
> dependencies from the supporting jar and several of its dependencies are
> using older jars (ehcache .07 vs 1.2 and so on).  While upgrading the
> supporting jar to the newer dependencies seems to fix the problem, I have a
> long road of testing to make sure the upgrade doesn't break anything in the
> functionality.  Time is, of course, the immediate issue.
>
> My question is there a way of compiling the supporting jar or the main app
> dependency so the main app won't use an older dependency.  For example the
> maven 1 compiled jar shows no dependencies when looking at the dependency
> hierarchy in the main app.  Yet once I point the main app POM to the newly
> compiled supporting jar, it's dependency hierarchy is loaded with the older
> jars and I have a long list of errors.  Any ideas?
>
> Hope it's making sense,
>     Ted
>
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Another-Maven-1-to-2-upgrade-issue-tp5754681.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--001a11c38a3e92d44c04dba9cda1--