continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject RE: Can't release project due to non released dependencies
Date Thu, 19 Jun 2008 13:55:25 GMT
That means that you are using a developers version also known as SNAPSHOT version. When you
release your project with a dependency to such a version, you create a instable release. When
there is a newer SNAPSHOT (those are not stable, mostly produced from trunk and can thus be
upgraded) which breaks your project, your release tag is broken. That's why the release plugin
advises you to not release your project.


1) Look for a non-SNAPSHOT version of the cps-printmanager and use that in your project.

2) Ask the developers of cps-printmanager to create a new release, and then use their new
version number

3) Use the allowTimestampedSnapshots property of the release:prepare goal and use a timed
snapshot of your dependency.


Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem

-----Original Message-----
From: bruno waes []
Sent: Thu 6/19/2008 15:46
Subject: Can't release project due to non released dependencies

[INFO] Updating local copy against the scm...
[INFO] Verifying that there are no local modifications...
[ERROR] org.apache.maven.shared.release.ReleaseFailureException: Can't
release project due to non released dependencies :
in project 'cps-printmanagerwebapp'

I get this error when trying to do a release (1.1.27) of my
cps-printmanagerwebapp project.

I have no idea what is causing this, 1.1.27-SNAPSHOT of printmanager is
available both in the snapshot repo (archiva) and local in the
.m2/repository of the continuum user.
View this message in context:
Sent from the Continuum - Users mailing list archive at

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