if you have it as a dependency of your project, then the correct way to
unpack the dependency is using dependency:unpack-dependencies with enough
includeGroupId, includeArtifactId, includeType specifications to limit the
execution to your dependency.
Additionally this will allow you to release
@maven.apache.org
Subject: RE: Dependency:unpack version problem
Use a property for the version + you can also use dependencyManagement.
But I doubt whether dependencyManagement version will flow to
dependency:unpack configurations. So property is best solution.
-Original Message-
From: Qureshi
subir.sasiku...@wipro.com wrote:
Use a property for the version + you can also use dependencyManagement.
But I doubt whether dependencyManagement version will flow to
dependency:unpack configurations. So property is best solution.
Maybe you should read Stephen's answer also ... ;-)
- Jörg
Fwiw the depmgt is checked in the unpack/copy goals... But Stephen is
right, unpack-dependencies is the right goal here.
--Brian (mobile)
On May 6, 2010, at 11:16 AM, Jörg Schaible joerg.schai...@gmx.de
wrote:
subir.sasiku...@wipro.com wrote:
Use a property for the version + you can
Hi all,
I am using the dependency:unpack goal of the maven dependency plugin to
unpack a library that is a dependency of the project itself. This
dependency is an internally maintaned library and is updated frequently.
So whenever the library is updated, we tell our developers to update
their
some configuration files from the library into the project, I would have
to tell our developers to update the dependency version in two places,
one in the dependencies section and other in the build section where
What happens when you omit the version in the one in the build section?
and/or
On Wed, May 5, 2010 at 6:14 PM, Qureshi,Shahzad [Ontario]
shahzad.qure...@ec.gc.ca wrote:
Is there is a better solution to this? Can I only change the version
number in the dependencies section and maybe read that version of this
dependency from there in my build section?
Try using a property.
: Thursday, May 06, 2010 3:44 AM
To: Maven Users List
Subject: Dependency:unpack version problem
Hi all,
I am using the dependency:unpack goal of the maven dependency plugin to
unpack a library that is a dependency of the project itself. This
dependency is an internally maintaned library
