[
https://issues.apache.org/jira/browse/FELIX-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864139#action_12864139
]
Christopher Blunck commented on FELIX-2324:
-------------------------------------------
I looked up standardization on execution environments in JVMs and I didn't get
very far.
It appears that "execution environments" is more of a concept than an actual
underlying artifact (accessible via a property or some other construct).
There appears to be some disagreement between
Bundle-RequireExecutionEnvironment values where some people cite "1.3" vs
"J2SE-1.3": http://www.mail-archive.com/d...@slf4j.org/msg00843.html
This smells like a very slipper slope from a framework perspective.
imo the framework should detect the current JVM version and then step backwards
in minor versions in an additive fashion, appending each value to the
"execution environments" that are supported.
For example...
If JVM 1.6.0_X is detected then the execution environments that should be
supported are: J2SE-1.6, J2SE-1.5, J2SE-1.4, J2SE-1.3, J2SE-1.2, J2SE-1.1,
J2SE-1.0.
If an application developer specifies
"-Dorg.osgi.framework.executionenvironment=foo" I'm on fence as to what
happens. In one hand I respect the application developer's perspective that
"foo" is the ONLY ee that their app suports. OTOH I also appreciate the
perspective that "foo" should be additive to the other sensed environments.
Perhaps a second system property is needed here?
Or ... ?
> Support execution environment so that OBR works properly
> --------------------------------------------------------
>
> Key: FELIX-2324
> URL: https://issues.apache.org/jira/browse/FELIX-2324
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Affects Versions: framework-2.0.5
> Reporter: Christopher Blunck
> Priority: Minor
> Fix For: framework-3.0.0
>
>
> Basic use case here is that I'd like to use Jackson within OBR. Jackson
> expresses a requirement on ee=J2SE-1.5. Felix Karaf doesn't have a facility
> for supported execution environments.
> I can set:
> JAVA_OPTS="-Dorg.osgi.framework.executionenvironment=J2SE-1.5"
> before I start karaf from the command line but this seems like a hack. It's
> very possible that I'll start Karaf using Sun's 1.6 JVM or an IBM JVM.
> Ideally at startup time Karaf could look at the runtime and determine the JVM
> version (at the very least). It could then expose the execution environment
> somehow (presumably in a way that OBR would understand).
> We should still be able to explicitly set the
> org.osgi.framework.executionenvironment system property but ideally it'd be
> additive to the ee's that Karaf senses when it starts up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
