Chris, > 2009/3/19 <[email protected]> > >> 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: [email protected] For additional commands, e-mail: [email protected]
