The following comment has been added to this issue:
Author: Ben Walding
Created: Fri, 17 Sep 2004 8:53 PM
Body:
Yeah I noticed this yesterday. Jetty does not like running out of an uberjar anymore.
(Basically it does a getPackage() on a class and this returns null under classworlds).
The bug is open in classworlds (CLASSWORLDS-1) and I'll be taking a look at it soon.
I've started committing some scripts to run the proxy not under in an uberjar (a .sh
and .bat file in src/bin). This will work around the problem.
The other upside from not using uberjar is that it starts a lot quicker - uberjar
introduces a 15 second startup time.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVENPROXY-14?page=comments#action_24206
---------------------------------------------------------------------
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
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-component-proxy
Assignee: Ben Walding
Reporter: Joerg Schaible
Created: Thu, 9 Sep 2004 6:48 AM
Updated: Fri, 17 Sep 2004 8:53 PM
Description:
maven-proxy fails with an exception at startup, if the properties file does not
contain at least an empty entry for proxy.list.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
