[
https://issues.apache.org/jira/browse/FELIX-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975590#action_12975590
]
luke w patterson commented on FELIX-2749:
-----------------------------------------
Hmm, I see now how things are a little more complicated.
My guess is that you could still get some use out of the plugin. (just a guess
though, I'm just a casual observer)
If you found/created/used a signature file for "OSGi foundation profile API",
and then explicitly marked the straying code with @IgnoreJRERequirement
https://animal-sniffer.dev.java.net/signature-checker.html
that might be a step forward. Not ideal, but a step forward.
"we try to keep them in separate execution paths so we can avoid them when
running on older JVMs"
Hopefully you're not using the "LinkageError pattern" as described
https://animal-sniffer.dev.java.net/signature-checker.html
, cause I've been burned by that when the JVM exercises it full rights to eager
resolution. I had to "opto-isolate" with a layer of pure reflection. Just a
thought, I haven't looked at the code to see how graceful fallback is handled.
> Boolean.parseBoolean() newly defined in Java5 should not be used.
> -----------------------------------------------------------------
>
> Key: FELIX-2749
> URL: https://issues.apache.org/jira/browse/FELIX-2749
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-3.0.7
> Environment: J2SE 1.4 with upcoming 3.0.7 release.
> Reporter: Ikuo YAMASAKI
> Assignee: Richard S. Hall
> Priority: Minor
> Fix For: framework-3.2.0
>
>
> For 3.0.7 release, the framework cannot run on J2SE 1.4 or CDC FP1.1 because
> Boolean.parseBoolean() is used.
> ---
> Exception in thread "main" java.lang.NoSuchMethodError:
> java.lang.Boolean.parseBoolean(Ljava/lang/String;)Z
> at
> org.apache.felix.framework.cache.BundleCache.<init>(BundleCache.java:113)
> at org.apache.felix.framework.Felix.init(Felix.java:593)
> at org.apache.felix.main.Main.main(Main.java:288)
> ---
> Those methods newly defined in Java 5 should not be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
