blob: 5ecb782d0bc84fb3a148a915d79c233ad86ea9b2 [file] [log] [blame]
{"componentChunkName":"component---src-pages-news-js","path":"/news/","result":{"data":{"allWordpressPost":{"nodes":[{"title":"Setting up an OpenJ9 Development Environment with Visual Studio Code + Docker + CMake","date":"19 November 2020","excerpt":"<p>Setting up a proficient development environment on a large project such as OpenJ9 with so many pieces in play can be a daunting task. Often times, setting up such a development environment and being able to navigate the codebase with familiar tools and with the full power of an IDE is worth the effort in terms of productivity. This blog post will guide you through setting up a development environment with a one-click build trigger, full Intellisense support, and full debugging support using Visual Studio Code, Docker, DevContainers extensions, and CMake.</p>\n","link":"https://blog.openj9.org/2020/11/19/setting-up-an-openj9-development-environment-with-visual-studio-code-docker-cmake/"},{"title":"Arraylets: What are They?","date":"02 June 2020","excerpt":"<p>Garbage Collectors (GCs) are responsible for allocating and deallocating objects making sure the running application run as smoothly as possible. There are many types of GC configurations out there, mark sweep, generational, region based, concurrent, parallel, reference counting [1] and a combination of these. The way we represent objects in each of these configurations, also&#8230;</p>\n","link":"https://blog.openj9.org/2020/06/02/arraylets-what-are-they/"}]},"allMarkdownRemark":{"edges":[{"node":{"html":"<!--\nCopyright (c) 2017, 2021 IBM Corp. and others\n\nThis program and the accompanying materials are made available under\nthe terms of the Eclipse Public License 2.0 which accompanies this\ndistribution and is available at https://www.eclipse.org/legal/epl-2.0/\nor the Apache License, Version 2.0 which accompanies this distribution and\nis available at https://www.apache.org/licenses/LICENSE-2.0.\n\nThis Source Code may also be made available under the following\nSecondary Licenses when the conditions for such availability set\nforth in the Eclipse Public License, v. 2.0 are satisfied: GNU\nGeneral Public License, version 2 with the GNU Classpath\nException [1] and GNU General Public License, version 2 with the\nOpenJDK Assembly Exception [2].\n\n[1] https://www.gnu.org/software/classpath/license.html\n[2] http://openjdk.java.net/legal/assembly-exception.html\n\nSPDX-License-Identifier: EPL-2.0 OR Apache-2.0 OR GPL-2.0 WITH Classpath-exception-2.0 OR LicenseRef-GPL-2.0 WITH Assembly-exception\n\nThe project website pages cannot be redistributed\n-->\n<h3>Eclipse OpenJ9 version 0.24.0 released</h3>\n<p><em>January 2021</em></p>\n<p>OpenJ9 version 0.24.0 supports OpenJDK version 8, 11, and 15.</p>\n<p>To learn more about support for OpenJ9 releases, including OpenJDK levels and platform support, see <a href=\"https://www.eclipse.org/openj9/docs/openj9_support/\" target=\"_blank\" rel=\"nofollow\">Supported environments</a>.</p>\n<p>For compatibility with the reference implementation, we've added support for the <code>JAVA_OPTIONS</code> environment variable. You can use this environment variable, which can be overridden by <code>OPENJ9_JAVA_OPTIONS</code>, to set command line options.</p>\n<p>The <code>-XX:[+|-]PortableSharedCache</code> option is now supported on IBM Z® and POWER® platforms. AOT-compiled code that is generated with this option is guaranteed to be portable across IBM z10 or newer microarchitectures on IBM Z platforms and IBM POWER8® or newer microarchitectures on POWER platforms.</p>\n<p>In earlier releases of OpenJ9, the <code>-XX:[+|-]ShareAnonymousClasses</code> option enables and disables the storage of VM anonymous classes in the shared classes cache. From OpenJ9 0.24.0 for OpenJDK 15 binaries, this option also controls the storage of hidden classes.\"</p>\n<p><strong>A number of additions and changes have been made to help you diagnose problems:</strong></p>\n<p>Several <code>jcmd</code> <code>Dump</code> commands can now take <code>request=&#x3C;requests></code> and <code>opts=&#x3C;options></code> parameters in addition to those already allowed.</p>\n<p>Optionally, <code>-Xcheck:jni</code> can now take an additional suboption, <code>abortonerror</code>, that provides diagnostic data when fatal JNI errors occur. </p>\n<p>To avoid confusion with the reference implementation of the <code>-Xlog</code> option, the <code>-Xsyslog</code> option replaces the existing OpenJ9 <code>-Xlog</code> option for message logging. For compatibility with the reference implementation, a limited set of <code>-Xlog</code> suboptions are supported.\nA new option, <code>-XX:[+|-]LegacyXlogOption</code>, controls how <code>-Xlog</code> is processed when set on the command line.</p>\n<p>The <code>jextract</code> utility gathers relevant files following a system dump. It is important that the utility is run from the same SDK that generated the dump. From this release, if the build ID of the <code>jextract</code> utility does not match the build ID of the SDK recorded in the system dump, an exception message is generated. To force <code>jextract</code> to continue, a new option, <code>-r</code>, is introduced.</p>\n<hr>\n<p>For all the details of changes and improvements in 0.24.0, read the <a href=\"https://www.eclipse.org/openj9/docs/version0.24/\" target=\"_blank\" rel=\"nofollow\">Version 0.24.0 \"What's New\" page</a> and see also the <a href=\"https://github.com/eclipse/openj9/blob/master/doc/release-notes/0.24/0.24.md\" target=\"_blank\" rel=\"nofollow\">OpenJ9 Release notes</a>.</p>"}}]}},"pageContext":{}},"staticQueryHashes":["965098542"]}