Re: Default JRE and Java plugin
I implemented the solution 5, reviews are welcome. http://anonscm.debian.org/cgit/pkg-java/java-common.git Emmanuel Bourg
Re: Default JRE and Java plugin
Le 07/10/2015 11:47, Matthias Klose a écrit :
> Not moving/or renaming the iceded-plugin to java-defaults would need
> rebuilds of the icedtea-web package on the version change. Not a big
> deal, but that's why I don't like 3.
I'm not sure to understand the rebuild issue. If we split
src:icedtea-web, we'll have:
- src:icedtea-web producing icedtea-7-plugin
- src:icedtea-8-web producing icedtea-8-plugin
- src:icedtea-9-web producing icedtea-9-plugin (in the future)
With an intermediate package we would have this dependency chain:
default-jre -> default-java-plugin -> icedtea-8-plugin
and with the solution 3 we would have:
default-jre -> icedtea-8-plugin
In both cases, a transition to Java 9 implies uploading
src:icedtea-9-web first and then switching the dependency in
src:java-common. Did I miss something?
Emmanuel Bourg
Default JRE and Java plugin
Hi all, I'm still rounding the corners for the switch to OpenJDK 8 and there is a remaining issue regarding the Java plugin. The src:icedtea-web package provides the icedtea-plugin package which pulls icedtea-7-plugin. Matthias would like to split src:icedtea-web and have one version per JRE supported. That would give a src:icedtea-8-web package building icedtea-8-plugin. The question is what do we do with the versionless icedtea-plugin package? It cannot remain in src:icedtea-web since the package will eventually go away. Since the package basically selects the default plugin its role could be taken over by src:java-common (the source of the default-jre/jdk packages). I see different solutions: 1. Move icedtea-plugin as is to src:java-common and make it select the default plugin (icedtea-7-plugin now, icedtea-8-plugin after the switch). 2. Move icedtea-plugin to src:java-common and rename it to default-java-plugin or default-jre-plugin (so if we switch to another implementation some day we don't have to rename the package). 3. Don't move icedtea-plugin but make default-jre recommends the default plugin. 4. Solution 1 + make default-jre recommends icedtea-plugin 5. Solution 2 + make default-jre recommends default-java-plugin I tend to favor the solution 3. With default-jre recommending the plugin we mimic the behaviour of the Oracle JRE since it includes the plugin by default, but the weak dependency makes it possible to uninstall the plugin afterward. What do you think? Emmanuel Bourg
Re: Default JRE and Java plugin
Le 07/10/2015 12:32, Matthias Klose a écrit : > as a recommends or as a suggests. I think 'recommends' would be better, so the plugin is installed automatically with the JRE, but it remains an optional dependency. > when you remove icedtea-8-plugin, you cannot directly re-install it > without relying on, or knowing the versioned name. True, so an intermediate default-java-plugin package has more value. We could probably make it provide icedtea-plugin too, so people using old tutorials can still get the right plugin. Emmanuel Bourg
Re: Default JRE and Java plugin
On 07.10.2015 11:34, Emmanuel Bourg wrote: Hi all, I'm still rounding the corners for the switch to OpenJDK 8 and there is a remaining issue regarding the Java plugin. The src:icedtea-web package provides the icedtea-plugin package which pulls icedtea-7-plugin. Matthias would like to split src:icedtea-web and have one version per JRE supported. That would give a src:icedtea-8-web package building icedtea-8-plugin. we have some duplicated code, but we don't want to release with two java versions anyway. The question is what do we do with the versionless icedtea-plugin package? It cannot remain in src:icedtea-web since the package will eventually go away. Since the package basically selects the default plugin its role could be taken over by src:java-common (the source of the default-jre/jdk packages). I see different solutions: 1. Move icedtea-plugin as is to src:java-common and make it select the default plugin (icedtea-7-plugin now, icedtea-8-plugin after the switch). 2. Move icedtea-plugin to src:java-common and rename it to default-java-plugin or default-jre-plugin (so if we switch to another implementation some day we don't have to rename the package). 3. Don't move icedtea-plugin but make default-jre recommends the default plugin. 4. Solution 1 + make default-jre recommends icedtea-plugin 5. Solution 2 + make default-jre recommends default-java-plugin I tend to favor the solution 3. With default-jre recommending the plugin we mimic the behaviour of the Oracle JRE since it includes the plugin by default, but the weak dependency makes it possible to uninstall the plugin afterward. What do you think? Not moving/or renaming the iceded-plugin to java-defaults would need rebuilds of the icedtea-web package on the version change. Not a big deal, but that's why I don't like 3. Whether recommends or suggests I don't care, but these should match with the ones in the versioned packages. Matthias
Re: Default JRE and Java plugin
On 07.10.2015 12:28, Emmanuel Bourg wrote: Le 07/10/2015 11:47, Matthias Klose a écrit : Not moving/or renaming the iceded-plugin to java-defaults would need rebuilds of the icedtea-web package on the version change. Not a big deal, but that's why I don't like 3. I'm not sure to understand the rebuild issue. If we split src:icedtea-web, we'll have: - src:icedtea-web producing icedtea-7-plugin - src:icedtea-8-web producing icedtea-8-plugin - src:icedtea-9-web producing icedtea-9-plugin (in the future) With an intermediate package we would have this dependency chain: default-jre -> default-java-plugin -> icedtea-8-plugin and with the solution 3 we would have: default-jre -> icedtea-8-plugin as a recommends or as a suggests. In both cases, a transition to Java 9 implies uploading src:icedtea-9-web first and then switching the dependency in src:java-common. Did I miss something? when you remove icedtea-8-plugin, you cannot directly re-install it without relying on, or knowing the versioned name.
Re: Default JRE and Java plugin
On 07.10.2015 13:10, Emmanuel Bourg wrote: We could probably make it provide icedtea-plugin too, so people using old tutorials can still get the right plugin. then introducing the need to rebuild the icedtea packages on a version change.
