Yeah I fixed that as well while I was at it. Should have been more explicit I guess.

I'll be dumping in a big chunk of changes shortly. Should resolve your snapshot issues, but will probably introduce some more - to good end - there are regression tests now for all the behaviour I can think of (you'll discover some things I didn't think of - mainly edge cases).

Jörg Schaible wrote:

Also for the original case, if no proxy.list is defined at all ?

[EMAIL PROTECTED] wrote on Sunday, September 19, 2004 4:40 AM:



Message:

  The following issue has been closed.

  Resolver: Ben Walding
      Date: Sat, 18 Sep 2004 10:39 PM

Rolled back to jetty 5.0.RC2. Works now.

The beginnings of a non uberjar setup are still in there, but
it's not created during the distribution creation, so uberjar
is still preferrred
---------------------------------------------------------------------
 View the issue: http://jira.codehaus.org/browse/MAVENPROXY-14

Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVENPROXY-14 Summary: Crash at startup with missing
proxy.list Type: Bug



--------------------------------------------------------------------- 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