Closed GoogleCodeExporter closed 9 years ago
Could you provide a fix as a pull request or patch?
Original comment by mosa...@gmail.com
on 5 Dec 2011 at 5:32
[deleted comment]
Sure i will try.
Original comment by drozddaw...@gmail.com
on 7 Dec 2011 at 12:43
[deleted comment]
[deleted comment]
[deleted comment]
The test causes this error. Today i will try fix.(Sorry for comments...)
Original comment by drozddaw...@gmail.com
on 8 Dec 2011 at 1:08
Attachments:
Ok i give pull request with fix and add patch here
Original comment by drozddaw...@gmail.com
on 8 Dec 2011 at 1:44
Attachments:
Patch applied, will go out with 2.6.1 release, let me know if you need it soon
Original comment by mosa...@gmail.com
on 8 Dec 2011 at 5:17
Original comment by mosa...@gmail.com
on 8 Dec 2011 at 5:26
No problem i make a new jar for my use ;). Sorry for code formatting i forgott
about it. Next time will be better.
Original comment by drozddaw...@gmail.com
on 8 Dec 2011 at 9:47
Great ;-) I will cut a release when some other fixes are in if somebody
provides something..
Original comment by mosa...@gmail.com
on 8 Dec 2011 at 9:50
this issue was only fixed in the single arg getPropertySafelyAsString, but it
still exists in the getPropertySafelyAsString(name, defaultThing) method which
still tries to call toString without checking for a null return from getProperty
Original comment by jroma...@gmail.com
on 17 Feb 2012 at 1:15
I am opening this again so I dont loose track of the last comment and the
related problem.
Original comment by mosa...@gmail.com
on 30 Apr 2012 at 6:59
This second related problem is now fixed in master and should be going out with
the 2.6.4 release.
Original comment by mosa...@gmail.com
on 30 Apr 2012 at 7:23
Original issue reported on code.google.com by
drozddaw...@gmail.com
on 4 Dec 2011 at 5:03Attachments: