GNU Classpath

The IcedTea project provides a harness to build the source code from OpenJDK using Free Software build tools, along with additional features such as a PulseAudio sound driver, the ability to build against system libraries and support for alternative ... [More] virtual machines and architectures beyond those supported by OpenJDK. This release updates our OpenJDK 6 support in the 1.13.x series with the October 2014 security fixes. If you find an issue with the release, please report it to our bug database under the appropriate component. Development discussion takes place on the distro-pkg-dev OpenJDK mailing list and patches are always welcome. Note that alternate virtual machines (e.g. CACAO, JamVM) will be broken by this release, until such a time as they introduce support for JVM_FindClassFromCaller, a new virtual machine interface function added by S8015256. Full details of the release can be found below. What’s New? New in release 1.13.5 (2014-10-14) Security fixes S8015256: Better class accessibility S8022783, CVE-2014-6504: Optimize C2 optimizations S8035162: Service printing service S8035781: Improve equality for annotations S8036805: Correct linker method lookup. S8036810: Correct linker field lookup S8037066, CVE-2014-6457: Secure transport layer S8037846, CVE-2014-6558: Ensure streaming of input cipher streams S8038899: Safer safepoints S8038903: More native monitor monitoring S8038908: Make Signature more robust S8038913: Bolster XML support S8039509, CVE-2014-6512: Wrap sockets more thoroughly S8039533, CVE-2014-6517: Higher resolution resolvers S8041540, CVE-2014-6511: Better use of pages in font processing S8041545: Better validation of generated rasters S8041564, CVE-2014-6506: Improved management of logger resources S8041717, CVE-2014-6519: Issue with class file parser S8042609, CVE-2014-6513: Limit splashiness of splash images S8042797, CVE-2014-6502: Avoid strawberries in LogRecord S8044274, CVE-2014-6531: Proper property processing Import of OpenJDK6 b33 OJ37: OpenJDK6-b32 cannot be built on Windows OJ39: Handle fonts with the non-canonical processing flag set OJ41: OpenJDK6 should be compatible with Windows SDK 7.1 OJ42: Remove @Override annotation on interfaces added by 2014/10/14 security fixes. S6967684: httpserver using a non thread-safe SimpleDateFormat S7033534: Two tests fail just against jdk7 b136 S7160837: DigestOutputStream does not turn off digest calculation when “close()” is called S7172149: ArrayIndexOutOfBoundsException from Signature.verify S8010213: Some api/javax_net/SocketFactory tests fail in 7u25 nightly build S8012637: Adjust CipherInputStream class to work in AEAD/GCM mode S8028192: Use of PKCS11-NSS provider in FIPS mode broken S8038000: java.awt.image.RasterFormatException: Incorrect scanline stride S8039396: NPE when writing a class descriptor object to a custom ObjectOutputStream S8042603: ‘SafepointPollOffset’ was not declared in static member function ‘static bool Arguments::check_vm_args_consistency()’ S8042850: Extra unused entries in ICU ScriptCodes enum S8052162: REGRESSION: sun/java2d/cmm/ColorConvertOp tests fail since 7u71 b01 S8053963: (dc) Use DatagramChannel.receive() instead of read() in connect() Backports S4963723: Implement SHA-224 S6578658: Request for raw RSA (NONEwithRSA) Signature support in SunMSCAPI S6753664: Support SHA256 (and higher) in SunMSCAPI S7033170: Cipher.getMaxAllowedKeyLength(String) throws NoSuchAlgorithmException S7044060: Need to support NSA Suite B Cryptography algorithms S7106773: 512 bits RSA key cannot work with SHA384 and SHA512 S7180907: Jarsigner -verify fails if rsa file used sha-256 with authenticated attributes S8006935: Need to take care of long secret keys in HMAC/PRF compuation S8017173, PR1688: XMLCipher with RSA_OAEP Key Transport algorithm can’t be instantiated S8049480: Current versions of Java can’t verify jars signed and timestamped with Java 9 Bug fixes PR1904: [REGRESSION] Bug reports now lack IcedTea version & distribution packaging information PR1967: Move to new OpenJDK bug URL format The tarballs can be downloaded from: http://icedtea.classpath.org/download/source/icedtea6-1.13.5.tar.gz http://icedtea.classpath.org/download/source/icedtea6-1.13.5.tar.xz We provide both gzip and xz tarballs, so that those who are able to make use of the smaller tarball produced by xz may do so. The tarballs are accompanied by digital signatures available at: http://icedtea.classpath.org/download/source/icedtea6-1.13.5.tar.gz.sig http://icedtea.classpath.org/download/source/icedtea6-1.13.5.tar.xz.sig These are produced using my public key. See details below. PGP Key: 248BDC07 (hkp://zimmermann.mayfirst.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 SHA256 checksums: 7bc21b8fa532c44279591372a77a76ae5976f54ae02ea8bdcd3dd7740511f1cb icedtea6-1.13.5.tar.gz daf5b5132e73091af7bdf1040ae234773fa62c4ee8600a4abfdb7b2db205ce3a icedtea6-1.13.5.tar.gz.sig 3579852895dcce8dcb0277b221c5b27d57baf7e642e9cbb92c1b67d9af9e2cbb icedtea6-1.13.5.tar.xz 8b5de1b8c814d9743c7531ad58e0cb1de1c40e56c7f2315ae01c45c36faa20f1 icedtea6-1.13.5.tar.xz.sig The checksums can be downloaded from: http://icedtea.classpath.org/download/source/icedtea6-1.13.5.sha256 A 1.13.5 ebuild for Gentoo is available. The following people helped with these releases: Andrew Hughes (all backports, release management) We would also like to thank the bug reporters and testers! To get started: $ tar xzf icedtea6-1.13.5.tar.gz or: $ tar x -I xz -f icedtea6-1.13.5.tar.xz then: $ mkdir icedtea-build $ cd icedtea-build $ ../icedtea6-1.13.5/configure $ make Full build requirements and instructions are available in the INSTALL file. Happy hacking! [Less]

Did you want to use GNUMail on NetBSD and were not even able to compile it? Do you run 64bit and had problems with GNUMail ?I am pleased to announce a new, maintenance release of Pantomime. Due to the inactivity of CollaborationWorld and Ludovic ... [More] , we(*) decided to import the sources in gnustep-nonfsf at gna.org.The download is at: http://download.gna.org/gnustep-nonfsf/Pantomime-1.2.2.tar.gzThis release contains updates and some important, long-needed fixes: * new res_init code for NetBSD which allows finally, after years, to run GNUMail on NetBSD! * enhanced portability to FreeBSD and OpenBSD * improved packaging hints in the makefiles * port to MacOS reinstantiated (10.3/10.4 tested) * extended 64bit fixes, including NSInteger/NSUInteger transitions were appropriate * enhanced crash catching, so that debugging is eased in the future * memory leaks fixed [Less]

I started hacking on firefox recently. And, of course, I’ve configured emacs a bit to make hacking on it more pleasant. The first thing I did was create a .dir-locals.el file with some customizations. Most of the tree has local variable settings in ... [More] the source files — but some are missing and it is useful to set some globally. (Whether they are universally correct is another matter…) Also, I like to use bug-reference-url-mode. What this does is automatically highlight references to bugs in the source code. That is, if you see “bug #1050501″, it will be buttonized and you can click (or C-RET) and open the bug in the browser. (The default regexp doesn’t capture quite enough references so my settings hack this too; but I filed an Emacs bug for it.) I put my .dir-locals.el just above my git checkout, so I don’t end up deleting it by mistake. It should probably just go directly in-tree, but I haven’t tried to do that yet. Here’s that code: ( ;; Generic settings. (nil . ;; See C-h f bug-reference-prog-mode, e.g, for using this. ((bug-reference-url-format . "https://bugzilla.mozilla.org/show_bug.cgi?id=%s") (bug-reference-bug-regexp . "\\([Bb]ug ?#?\\|[Pp]atch ?#\\|RFE ?#\\|PR [a-z-+]+/\\)\\([0-9]+\\(?:#[0-9]+\\)?\\)"))) ;; The built-in javascript mode. (js-mode . ((indent-tabs-mode . nil) (js-indent-level . 2))) (c++-mode . ((indent-tabs-mode . nil) (c-basic-offset . 2))) (idl-mode . ((indent-tabs-mode . nil) (c-basic-offset . 2))) ) In programming modes I enable bug-reference-prog-mode. This enables highlighting only in comments and strings. This would easily be done from prog-mode-hook, but I made my choice of minor modes depend on the major mode via find-file-hook. I’ve also found that it is nice to enable this minor mode in diff-mode and log-view-mode. This way you get bug references in diffs and when viewing git logs. The code ends up like: (defun tromey-maybe-enable-bug-url-mode () (and (boundp 'bug-reference-url-format) (stringp bug-reference-url-format) (if (or (derived-mode-p 'prog-mode) (eq major-mode 'tcl-mode) ;emacs 23 bug (eq major-mode 'makefile-mode)) ;emacs 23 bug (bug-reference-prog-mode t) (bug-reference-mode t)))) (add-hook 'find-file-hook #'tromey-maybe-enable-bug-url-mode) (add-hook 'log-view-mode-hook #'tromey-maybe-enable-bug-url-mode) (add-hook 'diff-mode-hook #'tromey-maybe-enable-bug-url-mode) [Less]

In the past weeks, quite some polish was added in windows support.First, there was a bug affecting Popup Menus and contextual menus that affected only certain computers. It was fixed. Then the controls were not properly initialized. Native ... [More] file-dialogs, for example, as well as upcoming print dialogs (work in progress by Gregory) did not fit the theme properly. On XP, Window 7 and Windows 8 they should follow the native look, instead they always got the "Win 95" look creating a strange mix.The fix requires initializing Windows' controls. I put the initialization code inside the WinUX theme loading. If it will not prove safe, then it needs to be moved into NSApplication. Furthermore, an XML resource file to enable the correct loading.I really does look nice, doesn't it? [Less]

I’ve been working on an odd Emacs package recently — not ready for release — which has turned into more than the usual morass of prefixed names and double hyphens. So, I took another look at Nic Ferrier’s namespace proposal. Suddenly it didn’t seem ... [More] all that hard to implement something along these lines, and after a bit of poking around I wrote emacs-module. The basic idea is to continue to follow the Emacs approach of prefixing symbol names — but not to require you to actually write out the full names of everything.  Instead, the module system intercepts load and friends to rewrite symbol names as lisp is loaded. The symbol renaming is done in a simple way, following existing Emacs conventions.  This gives the nice result that existing code doesn’t need to be updated to use the module system directly.  That is, the module system recognizes name prefixes as “implicit” modules, based purely on the module name. I’d say this is still a proof-of-concept.  I haven’t tried hairier cases, like defclass, and at least declare-function does not work but should. Here’s the example from the docs: (define-module testmodule :export (somevar)) (defvar somevar nil) (defvar private nil) (provide 'testmodule) This defines the public variable testmodule-somevar and the “private” function testmodule--private. [Less]

We are pleased to announce the release of IcedTea 2.5.2, “Back in the Groovy”! The IcedTea project provides a harness to build the source code from OpenJDK using Free Software build tools, along with additional features such as the ability to build ... [More] against system libraries and support for alternative virtual machines and architectures beyond those supported by OpenJDK. This release updates our OpenJDK 7 support with a number of regression fixes found in the previous 2.5.1 release. Mostly notably, it includes a backport of a regression fix. With the previous release, a number of Java tools and applications, including Groovy, were broken. This release should resolve these issues. If you find an issue with the release, please report it to our bug database under the appropriate component. Development discussion takes place on the distro-pkg-dev OpenJDK mailing list and patches are always welcome. Full details of the release can be found below. What’s New? New in release 2.5.2 (2014-08-29) Backports S8049480: Current versions of Java can’t verify jars signed and timestamped with Java 9 S8051012, LP1360392: Regression in verifier for <init> method call from inside of a branch Bug fixes PR1903: [REGRESSION] Bug reports now lack IcedTea version & distribution packaging information PR1948: Only try and symlink debuginfo if STRIP_POLICY is other than no_strip PR1948: Fix indenting PR1966: Move to new OpenJDK bug URL format RH1015432: java-1.7.0-openjdk: Fails on PPC with StackOverflowError (revised fix for PPC32) PPC & AIX port Adapt AIX port to 5049299: (process) Use posix_spawn, not fork, on S10 to avoid swap exhaustion Adapt aix to 8022507 Fix aix after 8022507: SIGSEGV at ParMarkBitMap::verify_clear() S8050942: PPC64: implement template interpreter for ppc64le S8050972: Concurrency problem in PcDesc cache The tarballs can be downloaded from: http://icedtea.classpath.org/download/source/icedtea-2.5.2.tar.gz http://icedtea.classpath.org/download/source/icedtea-2.5.2.tar.xz We provide both gzip and xz tarballs, so that those who are able to make use of the smaller tarball produced by xz may do so. The tarballs are accompanied by digital signatures available at: http://icedtea.classpath.org/download/source/icedtea-2.5.2.tar.gz.sig http://icedtea.classpath.org/download/source/icedtea-2.5.2.tar.xz.sig These are produced using my public key. See details below. PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07 SHA256 checksums: 6e36b5922d6a30b28a3387c60cf698461f12ae6471c9deab9c30763cb3505988 icedtea-2.5.2.tar.gz 77ebbd7b0c5e5878c779d04342013f9fd7e4c3ad12fa8388e556cbbe74fcce68 icedtea-2.5.2.tar.gz.sig 171e1ac6a549a9b15fec30fa308c777d0ac7498cc96058c4a2bcb0b0d0b45bf0 icedtea-2.5.2.tar.xz 985835869ccb2e6841ed41edf69b1d9f6aec1b3e5b4154009ca2561bbd8c01a8 icedtea-2.5.2.tar.xz.sig The checksums can be downloaded from: http://icedtea.classpath.org/download/source/icedtea-2.5.2.sha256 The following people helped with these releases: Andrew John Hughes (all other bug fixes and backports, release management) Chris Phillips (RH1015432) We would also like to thank the bug reporters and testers! To get started: $ tar xzf icedtea-2.5.2.tar.gz or: $ tar x -I xz -f icedtea-2.5.2.tar.xz then: $ mkdir icedtea-build $ cd icedtea-build $ ../icedtea-2.5.2/configure $ make Full build requirements and instructions are available in the INSTALL file. Happy hacking! [Less]

Ages and ages I wrote about letting Emacs code access the notification area.  I have more to say about it now, but first I want to bore you with some rambling thoughts and some history. The “notification area” is also called the “status icon area” or ... [More] the “systray” — it is a spot that holds some icons that are under control of various applications. I was a fan of the notification area since it first showed up in Gnome.  I recognized it instantly as the thing I wanted that I hadn’t realized I wanted. Now, as you know, the notification area has fallen on hard times.  It’s been removed in Gnome 3… I searched a bit for the rationale for this deletion, which as far as I can tell is just that some applications abused it, whatever that means; or that it was used inconsistently, which I think the web has conclusively proven is fine by users.  Coming from the Emacs perspective, where one can customize the somewhat-equivalent of the status area (see those recent posts on diminishing minor-mode lighters in the mode line…), and where a certain amount of per-mode idiosyncrasy is the norm, these seem like an inadequate reasons. However, the reason doesn’t really matter.  I love the notification area!  When I moved more of my daily desktop use back into Emacs (the tides are strong but slow, and take years to come in or go out), I hooked Emacs up to it, and made it a part of my basic configuration. It’s indispensable now.  What I particularly like about it is that it is both noticeable and unobtrusive — the former because I can have the icons blink on important events, and the latter because the icons don’t move around or obscure other windows. Ok!  You should use it!  And I totally plan to tell you how, but first some boring history. My original post relied on a hacked version of the Gnome zenity utility.  This turned out to be a real pain over time.  I had to rebuild it periodically, adding hacks (once removing chunks), etc.  Sharing it with others was hard.  And, for whatever reason, the patches in Gnome bugzilla were completely ignored.  Bah. A bit later I wrote a big patch to Emacs to put all this into the core.  That patch was rejected, more or less.  Bah two. Then even later I flirted with KDE for a bit.  Yes.  KDE had the nice idea to expose the notification area via dbus, and Emacs could talk dbus… so I did the obvious thing in elisp.  However the KDE notification area was pretty buggy and in the end I had to abandon it as well. So, it was back to zenity… until this week, during my funemployment.  I rewrote my hacks in Python.  This was so easy I wish I’d done it years and years ago. I’m not sure what the moral of this story is.  Maybe that my obsession is your gain.  Or maybe that I have trouble letting go. Anyway, the result is here, on github, or in marmalade.  You’ll need Python and the new (introspection-based) Python Gtk interfaces.  This of course is no trouble to install.  The package includes the base status icon API, plus basic UIs for ERC and EMMS.  Try it out and let me know what you think. [Less]

While streamlining my mode line, I wrote another little mode-line feature that I thought of ages ago — using the background of the mode-line to indicate the current position in the buffer. I didn’t like this enough to use it, but I thought I’d post ... [More] it since it was a fun hack. First, make sure the current mode line is kept: (defvar tromey-real-mode-line-format mode-line-format) Now, make a little function that format the mode line using the standard rules and then applies a property depending on the current position in the buffer: (defun tromey-compute-mode-line ()   (let* ((width (frame-width))      (line (substring         (concat (format-mode-line tromey-real-mode-line-format)             (make-string width ? ))         0 width)))     ;; Quote "%"s.     (setq line       (mapconcat (lambda (c)                (if (eq c ?%)                "%%"              ;; It's absurd that we must wrap this.              (make-string 1 c)))              line ""))     (let ((start (window-start))       (end (or (window-end) (point))))       (add-face-text-property (round (* (/ (float start)                        (point-max))                     (length line)))                   (round (* (/ (float end)                        (point-max))                     (length line)))                   'region nil line))     line)) We have to do this funny wrapping and “%”-quoting business here because the :eval form returns a mode line format — not just text — and because the otherwise appealing :propertize form doesn’t allow computations. Also, I’ve never understood why mapconcat can’t handle a character result from the map function.  Anybody? Now set this to be the mode line: (setq-default mode-line-format '((:eval (tromey-compute-mode-line)))) The function above changes the background of the mode line corresponding to the current window’s start and end positions.  So, for example, here we are in the middle of a buffer that is bigger than the window: I left this on for a bit but found it too distracting.  If you like it, use it. You might like to remove the mode-line-position stuff from the mode line, as it seems redundant with the visual display. [Less]

Thanks to Jonathan Lin and Spencer Hui some of the talks that were presented at the recent “bootcamp” are appearing on Air Mozilla and more will do so as we get them ready. They’re all in Air Mozilla’s engineering channel: https://air.mozilla.org/channels/engineering/

Thanks to everybody who commented on the JamVM 2.0.0 release, and apologies it's taken so long to approve them - I was expecting to get an email when I had an unmoderated comment but I haven't received any.To answer the query regarding Nashorn.  Yes ... [More] , JamVM 2.0.0 can run Nashorn.  It was one of the things I tested the JSR 292 implementation against.  However, I can't say I ran any particularly large scripts with it (it's not something I have a lot of experience with).  I'd be pleased to hear any experiences (good or bad) you have.So now 2.0.0 is out of the way I hope to do much more frequent releases.  I've just started to look at OpenJDK 9.  I was slightly dismayed to discover it wouldn't even start up (java -version), but it turned out to be not a lot of work to fix (2 evenings).  Next is the jtreg tests... [Less]