我怎样才能得到早期访问Oracle的Java更新,这样我就可以测试我的RIA,避免消防演习时,这些更新是公开的? [英] How can I get early access to Oracle Java updates, so I can test my RIA and avoid fire-drills when these updates are made public?

查看:239
本文介绍了我怎样才能得到早期访问Oracle的Java更新,这样我就可以测试我的RIA,避免消防演习时,这些更新是公开的?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有过我们的应用 <一个href=\"http://stackoverflow.com/questions/19400725/with-java-update-7-45-the-system-properties-no-more-set-from-jnlp-tag-property\">stop <一href=\"http://stackoverflow.com/questions/19393826/java-applet-manifest-allow-all-caller-allowable-$c$cbase\">working当客户安装7u45更新,我们想知道更多的东西,我们可以在未来做些准备好这些更新的前期,避免释放天的支持做噩梦。

Having had our application stop working when customers installed the 7u45 update, we're wondering what more we can do in the future to be ready for these updates up-front and avoid release-day support nightmares.

(根据<一个href=\"http://www.oracle.com/technetwork/java/javase/overview/jdk-version-number-scheme-1918258.html\">Java版本编号方案,下一个重要补丁更新,计划于1月14日,将7u51。接下来有限公司更新(日期不详)将7u60)

(Per the Java version numbering scheme, the next Critical Patch Update, planned for January 14, will be 7u51. The next Limited Update (date unknown) will be 7u60.)

我捅围绕Oracle和OpenJDK的网站,并没有发现什么特别有用。对Java SE的主要甲骨文页中有一个早期访问下载部分。它有潜力,但没有成功三个环节:

I've poked around the Oracle and OpenJDK websites, and not found anything particularly useful. The main Oracle page for Java SE has an Early Access Downloads section. It has three links that have potential, but don't pan out:

  • https://jdk7.java.net/, which still talks about 7u40 -- no mention of 7u45, let alone 7u51 or 7u60.

http://openjdk.java.net/projects/jdk7u/ ,它说:我们重新开放修复在jdk7u-dev的森林7u60,但似乎并没有提供任何pre-生成的二进制文件。这也是我不明白部署组件(小程序插件和Webstart的),我们过去的兼容性问题的主要来源,是否甚至部分的OpenJDK的开始。

http://openjdk.java.net/projects/jdk7u/, which says "We're open for fixes for 7u60 in the jdk7u-dev forest", but doesn't appear to provide any pre-built binaries. It's also not clear to me whether the deployment components (applet plug-in and webstart), the main source of our past compatibility issues, are even part of OpenJDK to begin with.

借助 Java的兼容性和性能计划听起来像我所想要的,但<一href=\"http://stackoverflow.com/questions/19434693/how-does-one-sign-up-for-the-jdk-cap-compatibility-and-performance-program-e\">nobody知道如何注册一个的。

The Java Compatibility and Performance Program sounds like just what I want, but nobody knows how to sign up for it.

一个答案以我上面的链接指向一个的的openjdk.java.net/browse/JDK-8023821\">OpenJDK bug报告是在8月申请回来。 (它有一个CAP的标签,这可能代表兼容性和性能?)所以,显然有些人能够对这些更新测试其应用程序。如何加入该俱乐部的任何指针是多少AP preciated!

An answer to the second question I linked above points to an OpenJDK bug report that was filed back in August. (It has a "CAP" label, which might stand for "Compatibility and Performance"?) So clearly some people are able to test their applications against these updates. Any pointers on how to join that club are much appreciated!

推荐答案

根据这个职位上的jdk7u-dev邮件列表 ,在 OpenJDK的纠错系统可以提供答案的一个子集。

OpenJDK Bug System

According to this post on the jdk7u-dev mailing list, the OpenJDK bug system may provide a subset of the answer.

邮件列表后说,臭虫与 CPU关键请求标签正在考虑纳入下一个CPU中和错误的<一个href=\"https://bugs.openjdk.java.net/issues/?jql=labels%3DCPU-critical-approved\">CPU-critical-approved标签已被批准列入下一个CPU英寸然而,在实践中,似乎他们使用更具体的标签。对于计划在2014年1月的7u51更新,标签显示为<一个href=\"https://bugs.openjdk.java.net/issues/?jql=labels%20%3D%20CPU14_01-critical-request\">CPU14_01-critical-request和<一个href=\"https://bugs.openjdk.java.net/issues/?jql=labels%20%3D%20CPU14_01-critical-approved\">CPU14_01-critical-approved.

The mailing list post says that bugs with the CPU-critical-request label are under consideration for inclusion in the next CPU and bugs with the CPU-critical-approved label have been approved for inclusion in the next CPU. However in practice, it seems that they're using more-specific labels. For the 7u51 update planned for January 2014, the labels appear to be CPU14_01-critical-request and CPU14_01-critical-approved.

您可以browse全套标签,以使有关标签为后续的CPU自己的猜测。您还可以看到错误的修正版7u51

You can browse the full set of labels to make your own educated guesses about labels for subsequent CPUs. You can also see bugs whose "fix version" is 7u51.

Java平台组,产品管理博客 看起来是局部信息的另一种途径。在<一个href=\"https://blogs.oracle.com/java-platform-group/entry/updated_security_baseline_7u45_impacts#comment-1382116031019\">this评论到<一个href=\"https://blogs.oracle.com/java-platform-group/entry/updated_security_baseline_7u45_impacts\">\"Updated安全基准(7u45)影响的Java 7u40和高安全性设置条目之前,甲骨文的Erik Costlow说:

The Java Platform Group, Product Management blog looks to be another avenue for partial information. In this comment to the "Updated Security Baseline (7u45) impacts Java 7u40 and before with High Security settings" entry, Erik Costlow of Oracle says:

一个我们创建这个博客的原因是,它给我们带来的一种方式
  提供尽可能多的信息,我们可以比它更已经
  在各种OpenJDK的邮件列表进行。

One of the reasons we created this blog is that it gives us a way of providing as much information as we can, even more than it already done on the various OpenJDK mailing lists.

有,我们不能提供有关提前通知了一些变化,
  我希望是保持其在最低限度。对于其他的变化,不仅是
  我们张贴他们在这里,我真的要出到其他
  项目不仅告诉他们,但(如适用)制作
  贡献。看到
  <一href=\"https://issues.apache.org/bugzilla/show_bug.cgi?id=55542\">https://issues.apache.org/bugzilla/show_bug.cgi?id=55542为
  例子。

There are some changes that we can't provide advance notice about, and my hope is to keep that to a minimum. For other changes, not only are we posting about them here, I am actually going out into other projects and not only telling them, but (as appropriate) making contributions. See https://issues.apache.org/bugzilla/show_bug.cgi?id=55542 for an example.

Java的兼容性和性能计划 是死的,根据我的Oracle客户经理。获得为CPU的一个类似的程序是严密控制的(甚至在Oracle)由于漏洞被反向工程的风险。 (我不是会员,不打算进一步追求它。)OpenJDK的是Oracle的$ P兼容性测试$ pferred方法,即使它是已知不会是会成为下一个CPU在什么位对位相同

Oracle Programs

The Java Compatibility and Performance Program is dead, according to my Oracle account manager. Access to an analogous program for CPUs is tightly controlled (even within Oracle) due to the risk of vulnerabilities being reverse-engineered. (I am not a member and do not plan to pursue it further.) OpenJDK is Oracle's preferred method of compatibility testing, even though it is known not to be bit-for-bit identical to what will be in the next CPU.

甲骨文也指我们在 Security在JavaOne 2013 ,尤其是一轨安全性增强的JRE谈话,他的幻灯片可在网上的一年。这些幻灯片,反过来说,上面提到的博客会给尽可能多的先进通知尽可能

Oracle also refers us to the Security Track at JavaOne 2013, in particular the "One Year of Security Enhancements in the JRE" talk, whose slides are available online. Those slides, in turn, say that the blog mentioned above will give "as much advanced notice as possible".

这篇关于我怎样才能得到早期访问Oracle的Java更新,这样我就可以测试我的RIA,避免消防演习时,这些更新是公开的?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆