Hi All, I'd like to get an idea if there are many people using the version range feature in the community. For those users using/relying version range, do you find any problems with it?
In our organisation, some people advocate the usage of version range but personally, I don't think it is robust enough for real world usage. Following problems are my main gripes that often stop me from runing maven on a day to day basis. * idea plugin errors (can't resolve artifacts with obscure errors). * dependencies resolution errors (various obscure NPE errors). * release plugin errors (can't release because we do clean install first and it will resolve to snapshot). * release plugin does not crystalise the actual version that has been resolved in the release pom that has been tagged. * version range depends on maven-metadata.xml the content of the file which can be errorneous. This is mainly based on Maven 2.0.6, because 2.0.7 gave us more NPE on resolving transitive dependencies. The problem also seems to happen with some projects and not others. Generally, we have about three or more layers of inhouse artifacts that are imported as dependencies across several maven modules. Like to hear any success/failure stories about this. Cheers, rOnn c. ###################################################################### DISCLAIMER: This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorized to copy or disclose all or any part of it without the prior written consent of Toyota. Opinions expressed in this email and any attachments are those of the sender and not necessarily the opinions of Toyota. Please scan this email and any attachment(s) for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. ######################################################################
