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-unsubscr...@maven.apache.org
For
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
Joachim Van der Auwera wrote:
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
the subject say it all: Is declaring scopes in the dependencyManagement
section of your parent POM a good idea or a bad idea?
Unless you are employing an approach wherein all of those deps will be
scope provided [because you are providing them in the application
server's shared libs folder], I
+1 here. I find it valuable to changing scope to provided.
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Friday, June 01, 2012 10:53 AM
To: Maven Users List
Subject: Re: Using scope in dependencyManagement: good idea or bad?
the subject say it all
a compile time dependency
to the needed library.
LieGrue,
strub
- Original Message -
From: Thiessen, Todd (Todd) tthies...@avaya.com
To: Maven Users List users@maven.apache.org
Cc:
Sent: Friday, June 1, 2012 5:20 PM
Subject: RE: Using scope in dependencyManagement: good idea or bad
5:20 PM
Subject: RE: Using scope in dependencyManagement: good idea or bad?
+1 here. I find it valuable to changing scope to provided.
-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com]
Sent: Friday, June 01, 2012 10:53 AM
To: Maven Users List
Subject: Re: Using
