Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0.1
-
Fix Version/s: 1.1-beta-1
-
Component/s: None
-
Labels:None
-
Environment:MacOSX 10.3.6 / JDK v1.4.2
-
Number of attachments :
Description
If build.properties is defined like this:
maven.proxy.host = 192.168.1.27
maven.proxy.port = 80
maven.proxy.username = username
maven.proxy.password = password
maven.proxy.ntlm.domain = domain
Then maven bombs out with a NullPointerException like this:
Graham-Leggetts-Computer:~/src/standard/autobahn minfrin$ maven site
__ __
| \/ | __ Apache_ ___ | |||||
| \/ | / ` \ V / -) ' \ ~ intelligent projects ~ | |||||
| _ | _,_ | _/___ | _ | _ | v. 1.0.1 |
|---|
Attempting to download jdepend-2.7.jar.
Error retrieving artifact from http://www.ibiblio.org/maven/jdepend/jars/jdepend-2.7.jar: java.lang.NullPointerException
WARNING: Failed to download jdepend-2.7.jar.
BUILD FAILED
File...... /Users/minfrin/.maven/cache/maven-xdoc-plugin-1.8/plugin.jelly
Element... attainGoal
Line...... 693
Column.... 57
The build cannot continue because of the following unsatisfied dependency:
jdepend-2.7.jar
Total time: 5 seconds
Finished at: Wed Dec 01 15:10:41 SAST 2004
What should happen is that a valid error message be returned to the user as to whatever is missing. "NullPointerException" says nothing to the user.
Activity
Don't think this is related to NTLM authentication. It works for me at the office (using 1.0 btw). I think the problem could be not specifying ntlm.username in this case ? (Can try to test that in about 2 weeks, am on a holiday now 
Ehh the nltm.host I use these settings :
maven.proxy.ntlm.host=our proxy server hostname
maven.proxy.ntlm.domain=ODIN
maven.proxy.username=me
maven.proxy.password=whatever
maven.proxy.host=our proxy server hostname
maven.proxy.domain=ODIN
maven.proxy.port=8080
I use these settings :
maven.proxy.ntlm.host=our proxy server hostname
maven.proxy.ntlm.domain=ODIN
maven.proxy.username=me
maven.proxy.password=whatever
maven.proxy.host=our proxy server hostname
maven.proxy.domain=ODIN
maven.proxy.port=8080
please run maven -e site and post the stack trace (if it still doesn't show, you might need to run maven -X site).
You're correct, it should not cause a NPE.