Tamás Cservenák wrote:
Hi,
Not quite. Proximity is (almost) plain HTTP proxy, but IT DOES have
knowledge about maven reposes (see repository browsing or the use of
"?repositoryId=central" URL parameter.), but only as separate "storages".
What it does not have is STATE, it cannot distuingish the two consecutive
HTTP GET commands from same M2, once for metadata and once for POM.
That is not the problem, the problem is that the metadata from all the
repositories has to be _merged_ and dispatched properly by proximity.
That is why any plain http proxy will fail acting as a repository for Maven.
The solution should be in POM (Maven).
How can Maven solve this problem? Maven will properly merge the metadata
from the different repositories but Proximity is effectively stopping
half of the data coming through.
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
