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 (athena.apache.org: local policy)
Message-ID: <4FC8C656.2070807@progs.be>
Date: Fri, 01 Jun 2012 15:40:38 +0200
From: Joachim Van der Auwera <joachim@progs.be>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: users@maven.apache.org
Subject: Re: Using scope in dependencyManagement: good idea or bad?
References: <4FC8BE16.7040500@st.informatik.tu-darmstadt.de>
In-Reply-To: <4FC8BE16.7040500@st.informatik.tu-darmstadt.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

In my experience a bad idea (bitten by this in the past). If the same 
dependency is mentioned in dependencyManagement in various places, then 
you may end up with the wrong scope.

I use dependencyManagement to specify the version and possibly 
exclusions. Scope is still managed in the dependency declaration itself.

Kind regards,
Joachim

On 01-06-12 15:05, Andreas Sewe wrote:
> Hi all,
>
> the subject say it all: Is declaring scopes in the dependencyManagement
> section of your parent POM a good idea or a bad idea?
>
> Best wishes,
>
> Andreas
>
> ---------------------------------------------------------------------
> 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