You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/03/04 08:47:05 UTC
[jira] [Resolved] (SLING-1481) JRE packages are exported with wrong
version
[ https://issues.apache.org/jira/browse/SLING-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1481.
-------------------------------------
Resolution: Not a Problem
I think this has been solved in the meantime
> JRE packages are exported with wrong version
> --------------------------------------------
>
> Key: SLING-1481
> URL: https://issues.apache.org/jira/browse/SLING-1481
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Affects Versions: Launchpad Base 2.1.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> FELIX-995 discusses the issue of the version number to use for the JRE provided packages. After some discussions, Thomas Watson of the Eclips project proposes in [1] to use the Execution Environment Name of the platform as the version qualifier string and setting the major/minor/micro version to 0.0.0 (Quoting [1]):
> I would use the Execution Environment string for the VM instead of jre-1.6 though (e.g. 0.0.0.JavaSE-1.6, 0.0.0.J2SE-1.4 etc.). There is an
> issue for what the qualifier should be for embedded VMs since '/' is not a valid character in a qualifier (e.g. CDC-1.1/Foundation-1.1) We
> would have to substitute '_' or something else for '/'.
> I think we might want to the same in our Sling framework launcher.
> WDYT ?
> [1] https://issues.apache.org/jira/browse/FELIX-995?focusedCommentId=12855398&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12855398
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)