You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Dave Hoffer <DH...@xrite.com> on 2007/04/17 22:55:16 UTC
[m2.0.6] why does my release complain about unreleased snapshots?

I have upgraded to 2.0.6 (because that is what came with the upgrade of
TeamCity(TC) 2.0) and releases fail because of non released
dependencies.  However I am not specifying the use of any SNAPSHOTS in
my POM.  Here is my POM entry for this dependency:

<dependency>
    <groupId>com.xrite</groupId>
    <artifactId>xrite-colorlib-api</artifactId>
    <version>[1.0,)</version>
</dependency>

Here is the TC log:

[16:45:26]: [release:prepare]
[16:45:26]: Resuming release from phase 'check-dependency-snapshots'
[16:45:26]: Checking dependencies and plugins for snapshots ...
[16:45:26]:
------------------------------------------------------------------------
[16:45:26]: BUILD FAILURE
[16:45:26]:
------------------------------------------------------------------------
[16:45:26]: Can't release project due to non released dependencies :
com.xrite:xrite-colorlib-api:jar:1.21-SNAPSHOT:compile in project
'xrite-commons' (com.xrite:xrite-commons:jar:1.36-SNAPSHOT)
[16:45:26]:
------------------------------------------------------------------------
[16:45:26]: For more information, run Maven with the -e switch
[16:45:26]:
------------------------------------------------------------------------
[16:45:26]: Total time: 1 minute 
[16:45:26]: Finished at: Tue Apr 17 16:45:26 EDT 2007
[16:45:26]: Final Memory: 11M/28M
[16:45:26]:
------------------------------------------------------------------------
[16:45:26]: Can't release project due to non released dependencies :
com.xrite:xrite-colorlib-api:jar:1.21-SNAPSHOT:compile in project
'xrite-commons' (com.xrite:xrite-commons:jar:1.36-SNAPSHOT)

My POM's repository section does not specify access to SNAPSHOTS:

<repositories>
        <repository>
            <id>inhouse</id>
            <url>http://XRBUILD2:81/proximity/repository/inhouse</url>
        </repository>
        <repository>
            <id>public</id>
            <url>http://XRBUILD2:81/proximity/repository/public</url>
        </repository>
</repositories>

Was there a change in how m2.0.6 deals with dependencies using set
notation?  Why might this be failing?

-Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org