[jira] [Comment Edited] (SLING-10288) FelixFrameworkScanner sets framework properties always for current Java version

["Karl Pauls (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318104#comment-17318104 ] 

Karl Pauls edited comment on SLING-10288 at 4/9/21, 4:07 PM:
-------------------------------------------------------------

[~kwin], not easily. The framework is calculating some stuff for us. I guess you could try to externalize that but it probably would be easier to somehow fix the java.home thing.


was (Author: karlpauls):
[~kwin], not easily.

> FelixFrameworkScanner sets framework properties always for current Java version
> -------------------------------------------------------------------------------
>
>                 Key: SLING-10288
>                 URL: https://issues.apache.org/jira/browse/SLING-10288
>             Project: Sling
>          Issue Type: Bug
>          Components: Feature Model Analyser
>            Reporter: Konrad Windszus
>            Priority: Major
>
> Sometimes the analyser is executed with a different java version than the one executing the actual OSGi container. There should be a possibility to explicitly set a Java version.
> Currently the framework properties are gathered in a dedicated java process executing https://github.com/apache/sling-org-apache-sling-feature-analyser/blob/730b7d3297ab9f17f484e7b557e4ec47c3d9b3e9/src/main/java/org/apache/sling/feature/scanner/impl/fwk/FrameworkPropertiesGatherer.java#L41. That new process always takes the current  {{java.home}} which therefore returns the wrong properties (i.e. the ones for the current  java version instead of the one used to execute the framework).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)