Or even just checking System property java.version.
-Tom
On Fri, 17 Feb 2006, Charles O Nutter defenestrated me:
> The getenv from 1.4- is, as you mention, deprecated. That won't
> prevent it from being called. However the 1.5 version has a new
> signature, so searching for it using reflection
The getenv from 1.4- is, as you mention, deprecated. That won't
prevent it from being called. However the 1.5 version has a new
signature, so searching for it using reflection and catching NSME
should be fine.
1.4- version: String getenv(String)
1.5 version: Map getenv()
On 2/17/06, Galarneau, Ne
A comment on this implementation:
My impression is that Java 1.4.2 won't throw NoSuchMethodException
as getenv in that version is deprecated, not missing.
This would mean that you could call getenv() directly instead of
reflectively as long as it was only called on Java 5.
Neil
+protected
We have looked at using code coverage tools in the past, and while
they're useful they don't help us ensure we're behaving correctly. We
mostly have to run and re-run tests and applications to find all the
holes. We will try to look at JIRA though...and I think it's been
mentioned in the past.
The
Do you have a list of existing bugs, so I don't send you things that
have already been logged? Have you considered using JIRA
(http://www.atlassian.com/software/jira/)? You can get a free license
for Open Source projects. I use it here at work, and it's really a
phenomenal application.
-Ben
On
Hi,
I just saw this out:
http://seclib.blogspot.com/2006/02/first-release-of-rubyfront.html
I'm not entirely sure what they want to do with it, though (the site
says something about creating a checking tools);
murphee
--
Blog @ http://jroller.com/page/murphee
---
