Re: Aren't ranges allowed when releasing?

[Stephen Connolly <st...@gmail.com>]

Please direct your questions to the maven users list.  I am not your
personal guru ;-)

-Stephen

2009/3/19 <ch...@warpspeed.com.au>

> Hi Stephen,
>
> I've just got this to worry about.
>
> I'm trying to release a project, that has these dependencies in it. It
> works fine for install/package etc, but only when releasing does it
> complain.
>
> If it can choose the correct one to compile and package against, why can we
> not trust it to choose it when releasing?
>
> ta.
>
> -Chris
>
> PS: If you could please reply to chgraham@au1.ibm.com, I'd be most
> appreciatative.
>
> Hi Chris,
> Release of Batch Data Service failed due to following dependencies.
>
> [INFO] Building BatchDataServices
> [INFO]    task-segment: [release:prepare, release:perform]
> (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [release:prepare]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: svn --username sctbuild --password *****
> --non-interactive status
> [INFO] Working directory:
> /var/WebSphere/Hudson/jobs/eswm-Common-BatchDataServices/workspace
> [INFO] Checking dependencies and plugins for snapshots ...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Can't release project due to non released dependencies :
>    com.ibm.sct.common:Foundation:jar:[3.0.0.0,4.0.0.0):provided
>    com.ibm.sct.common:MIL:jar:[3.0.0.0,4.0.0.0):provided
>    com.ibm.sct.common:TelstraCustom:jar:[3.0.0.0,4.0.0.0):provided
> in project 'BatchDataServices'
> (com.ibm.sct.common:BatchDataServices:jar:3.0.0.1-SNAPSHOT)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
>
>
>

Re: Aren't ranges allowed when releasing?

[Ringo De Smet <ri...@gmail.com>]

Chris,

> 2009/3/19 <ch...@warpspeed.com.au>
>
>> I'm trying to release a project, that has these dependencies in it. It
>> works fine for install/package etc, but only when releasing does it
>> complain.
>>
>> If it can choose the correct one to compile and package against, why can we
>> not trust it to choose it when releasing?

>> [INFO] Can't release project due to non released dependencies :
>>    com.ibm.sct.common:Foundation:jar:[3.0.0.0,4.0.0.0):provided
>>    com.ibm.sct.common:MIL:jar:[3.0.0.0,4.0.0.0):provided
>>    com.ibm.sct.common:TelstraCustom:jar:[3.0.0.0,4.0.0.0):provided
>> in project 'BatchDataServices'
>> (com.ibm.sct.common:BatchDataServices:jar:3.0.0.1-SNAPSHOT)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch

Do you have releases of all the dependent modules with version number
3.0.0.0 ? I suspect not!

Second, your version ranges are defined very strictly. Maven has a
convention for 3 part build numbers: major.minor.build. If you want to
specify the latest release within the same release (e.g. 2.5), then
specify your range as:

[2.5,2.6)

This will match a release 2.5.x with x the highest number available
from your Maven repository.

Ringo

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