Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of baerrach@gmail.com designates
 209.85.128.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <B8D164BED956C5439875951895CB4B221882805C@WABOTH9MSGUSR8C.ITServices.sbc.com>
References: 
 <B8D164BED956C5439875951895CB4B221882805C@WABOTH9MSGUSR8C.ITServices.sbc.com>
Date: Tue, 14 Jan 2014 11:17:42 +1030
Message-ID: 
 <CADVp3v9QAzHx3qZabYLoECy+v0tJx38zywMVJkVvEB=woocPYg@mail.gmail.com>
Subject: Re: Is it possible to deliberately have two dependencies with the
 same groupid, artifactid, and packaging, but different version?
From: Barrie Treloar <baerrach@gmail.com>
To: Maven Users List <users@maven.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 14 January 2014 10:54, KARR, DAVID <dk068x@att.com> wrote:
> I have a situation where it would be convenient for my pom to have two de=
pendencies that are almost identical, only being different by the version. =
 The makeup of the artifact is such that it would be safe (and intended) to=
 use both of them.  The Java package used in each is similar, but different=
.  The package will vary along with the version number.
>
> Will dependency resolution and the EAR plugin (and any other mechanism th=
at lists dependencies) have any trouble with this?

Can you describe why you think this would be convenient?
Have you looked at classifiers?
http://stackoverflow.com/questions/8040964/how-to-use-or-abuse-artifact-cla=
ssifiers-in-maven

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org