Solution for maven error "Can't release project due to non released dependencies":
Are you trying to use the maven release plugin to do a release and running into the below error:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Can't release project due to non released dependencies :
integration:integration-api:jar:2.0-SNAPSHOT:compile
in project 'myproject' (integration:myproject:pom:2.0-SNAPSHOT) read on for a solution.



When doing a maven release using the release plugin, specifically when running mvn release:prepare you might run into below issue:

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Can't release project due to non released dependencies :
integration:integration-api:jar:2.0-SNAPSHOT:compile
in project 'myproject' (integration:myproject:pom:2.0-SNAPSHOT)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------

Developers are often confused about the above message. The typical reaction is to look at the maven repository or settings.xml to confirm if the jar exists in the snapshot repository. Those are not the places to look at.

This is a limitation of mvn release plugin. It seems maven release plugin does not allow snapshot dependencies during mvn release:prepare due to instabilities that can be caused by new snapshots. Please keep in mind that a snapshot build is a developer build that might undergo multiple developer changes (sometimes even broken stuff). Maven release plugin has a “allowtimestampedsnapshots” flag which is expected to allow you to workaround this. But it does not really work.

So, your only option is towait for a regular release of your dependency and then use the version number in your pom.xml dependency section.