Hi We have a jar repository that was created a while back during the maven one time. It is not a maven repo. Now that we are slowly migrating to maven 2/3, we create a wrapper around the repo to be able to send artifact to way maven expects them. This will disappear once all our projects are migrated to maven. We use nexus as our main repo.
The problem we are having, is that even if there is a new version of a SNAPSHOT, the newer version is not downloaded. We added the updatePolicy to always for all our snapshot repos and it works for Nexus but not "our repo". We are trying to understand how it works to be able to mimic the behavior. We saw the request for the metadata.xml come and we thought that it was the solution to our problem, but it seems that we are missing something. The way we understood the format of this file is as follow <metadata> <groupId>the group id</groupId> <artifactId>the artifact id</artifactId> <versioning> <versions> <version></version> <version></version> <version></version> ... </versions> <lastUpdated>the formatted timestamp of the most up to date version</lastUpdated> </versioning> </metadata> Now one question would be: Does the order of the version matter? How does it really works? I am doing some remote debugging into the maven code to try to understand the process, but I'd like to see if someone could also point me in the right direction. Thanks a lot Adrien Gracia Bank of America ---------------------------------------------------------------------- This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.
