 How to best deal with broken Maven2 meta-data [message #545176] |
Tue, 06 July 2010 18:39 |
Eclipse User |
|
|
|
I'm under the impression (please correct me if I'm wrong) that Buckminster currently requires each Maven2 repository it consumes to contain valid maven-metadata.xml resources at all times. Maven itself, on the other hand, will only use this information as a subtle hint on how to best resolve open version ranges such as "[3.1-alpha1,)".
Unfortunately, quite a number of public Maven2 repositories (e.g. SpringSource or even iblio) have problems with the consistency of their maven-metadata.xml files at present:
Thus I wonder: Is there a way to force Buckminster to simply "probe" for matching POM/JAR files of a given Maven2 component, especially if the given designated version of the dependency itself is already quite explicit/unambiguous on what artefact would have to be retrieved?
Thanks in advance,
Chris
|
|
|
Powered by
FUDForum. Page generated in 0.02793 seconds
Home