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.
Solutions: 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. Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl -----Original Message----- From: bruno waes [mailto:[EMAIL PROTECTED] Sent: Thu 6/19/2008 15:46 To: [email protected] 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 : mypackage.printmanager:cps-printmanager:jar:1.1.27-SNAPSHOT:compile in project 'cps-printmanagerwebapp' (mypackage:cps-printmanagerwebapp:war:1.1.27-SNAPSHOT) 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: http://www.nabble.com/Can%27t-release-project-due-to-non-released-dependencies-tp18009379p18009379.html Sent from the Continuum - Users mailing list archive at Nabble.com.
