Unless you can post a project to github that demonstrates differential
behavior everywhere, or use mvn -X or wireshark to deliver an analysis
of *how* 3.0.3 is hitting the network differently than 2.2.1, you're
unlikely to get much succor here.

It would really help you if you could convince your corporate
Archiva-ists to configure it to work as a cache for the internet.

Or if you quietly put a copy of Archiva or Nexus for those purposes on
your own machine :-)

On Mon, May 16, 2011 at 12:54 PM, Andrew Robinson
<[email protected]> wrote:
> Archiva is being used to serve our internal packages of our company, it is
> not being used to serve dependencies from internet repositories. So no I
> cannot send all requests through Archiva.
>
> It may be as simple as a linux kernel issue with e1000e driver (dell
> latitude E6410). It has caused me issues in Ubuntu in 10.10 and could be
> still some issues in 11.04. It is hard to say as there is not much to debug
> with at this point and I am not seeing any obvious system errors or anything
> to troubleshoot with.
>
> On Mon, May 16, 2011 at 10:34 AM, Wayne Fay <[email protected]> wrote:
>
>> > Any advice on this? Should I be opening a maven bug? It is really killing
>> my
>> > productivity as I have to babysit every build and keep aborting it and
>> > restarting it several times until all updates (mostly snapshots per day)
>> are
>> > downloaded.
>>
>> If this was typical then we would see similar complaints from lots of
>> people. Clearly something is special about the way you have things
>> configured or something else in your environment. I'm not sure how you
>> expect anyone here to diagnose this class of problem.
>>
>> Did you reconfigure your proxy and settings.xml so all requests are
>> going through Archiva? I see that as a pre-requisite before talking
>> about anything else.
>>
>> Wayne
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to