Bug #214
NPE creating index
| Status: | New | Start: | 06/17/2009 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
Description
C:\apps\supose-0.6.1-385\bin>supose scan --url 'someUrl' --create --index sandbox --username user --password somePassword
Exception in thread "main" java.lang.NullPointerException
at com.soebes.supose.repository.Repository.<init>(Repository.java:78)
at com.soebes.supose.cli.SuposeCLI.runScan(SuposeCLI.java:135)
at com.soebes.supose.cli.SuposeCLI.main(SuposeCLI.java:96)
I suspect I got this NPE because my password (obviously not shown here..) has exclamation marks in it.
I tried my username/password with --username --password to 'svn ls' and it worked fine.
History
Updated by Karl Heinz Marbaise 1065 days ago
Hi Tim,
first of all thanks for using SupoSE...
on the other hand i would like to know i you have tried to quote the password which contains the exclamation marks?
And the other question is: Is the repository URL http or https or svn or may be file protocol ?
BTW: What version of Subversion do you use on the server side which you like to scan ?
Exception in thread "main" java.lang.NullPointerException at com.soebes.supose.repository.Repository.<init>(Repository.java:78) at com.soebes.supose.cli.SuposeCLI.runScan(SuposeCLI.java:135) at com.soebes.supose.cli.SuposeCLI.main(SuposeCLI.java:96)
Based on that it seemed to be a relationship with the authentication...but i'm not sure if the reason is the usage of exclamation marks...
Kind regards
Karl Heinz Marbaise
I suspect I got this NPE because my password (obviously not shown here..) has exclamation marks in it.
I tried my username/password with --username --password to 'svn ls' and it worked fine.
Updated by Tim Harsch 1065 days ago
Don't know server SVN version. Though it was put in place with the latest about 1.5 years ago, so it isn't real old.
I did try quoting, no luck.
repo URL is https://
One comment I might make is that even if a fix like quoting the password were to fix it, you might want to take this opportunity to clean up the source so it doesn't throw an NPE but a meaningful message. I know sometimes that is easier said than done, but...
Thanks for creating SupoSE.
Updated by Karl Heinz Marbaise 1065 days ago
Hi Tim,
Tim Harsch wrote:
Though it was put in place with the latest about 1.5 years ago, so it isn't real old.
That depends ;-)
I did try quoting, no luck. repo URL is https://
/>
Have you checked which Java Runtime Version you are using?
May you have to configure the SSL connection on the Java side...
Take a look at this
One comment I might make is that even if a fix like quoting the password were to fix it, you might want to take this opportunity to clean up the source so it doesn't throw an NPE but a meaningful message.
If that had been the case i can say that this had been a problem of the shell e.g. particular characters like "%" on Windows or "$" on unix like things...so in that case i couldn't change anything about that....
On the other hand you're right about the meaningful messages, but as you mentioned it's not so easy...
I know sometimes that is easier said than done, but...
And last but not least this is an Open Source project may you can contribute a patch for the problem ?
Kind regards
Karl Heinz Marbaise