Well after all, I didn't really fix this. This is an issue that seems to come
and go. Here is the contents of maven-metadata-inhouse.xml
<?xml version="1.0" encoding="UTF-8"?><metadata>
<groupId>com.xrite</groupId>
<artifactId>xrite-colorlib-api</artifactId>
<version>1.0</version>
<versioning>
<release>1.7</release>
<versions>
<version>1.0</version>
<version>1.1</version>
<version>1.2</version>
<version>1.3</version>
<version>1.5</version>
<version>1.7</version>
</versions>
<lastUpdated>20061006012356</lastUpdated
This file is correct on the server but when Proximity downloads it to local
user dir it corrupts the file by not closing the ending tags. What may be the
cause of this?
-dh
________________________________________
From: Dave Hoffer
Sent: Tuesday, October 03, 2006 1:52 PM
To: 'Maven Users List'
Subject: Why does my install goal fail?
I have seen a problem lately where the install goal will fail. The problem is
that the meta data downloaded is corrupt; the ...metadata-inhouse.xml file
starts out correct but is missing the bottom of the file. I.e. it is missing
the lastUpdated tag section and closing tags.
This seems to occur when we have dependencies that depend on other dependencies
specified using set notation for the version. For example, I have a dependency
on xrite-imaging; xrite-imaging has a dependency on xrite-commons with version
of [1.0,). Maven fails when it builds the ...metadata-inhouse.xml file for
xrite-commons.
I am using Proximity as my http artifact server.
Why is this happening? This used to work (but our plugin versions have changed
somewhat).
-dh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
