maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Connolly <>
Subject Re: Dependency:unpack version problem
Date Thu, 06 May 2010 06:04:27 GMT
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 with the maven release plugin as
dependency:unpack-dependencies searches the reactor while dependency:unpack
does not [and therefore requires that the dependency is installed in the
local repository]

That allows you to specify the version in one place only (probably the
dependencyManagement section of your root pom


On 5 May 2010 23:14, Qureshi,Shahzad [Ontario] <>wrote:

> 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 version of the dependency and everything works the way we wanted.
> The problem is that, now that I am using the dependency:unpack to copy
> 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
> I am doing the unpacking
> 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?
> Or any other ideas?
> thanks
> --------------------------------------------
> Shahzad Qureshi

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message