mirror of
https://github.com/processing/processing4.git
synced 2026-01-25 09:21:07 +01:00
c14695476e
Moves to Java11 and OpenJDK via AdoptOpenJDK within the processing4 train using a squash of sampottinger processing fork's java11 branch. **Primary required changes:** Some changes directly support OpenJFX / OpenJDK 11: - Response to image loading changes caused by [JEP 320](https://openjdk.java.net/jeps/320) - Use of jmodules as necessitated by [JEP 261](https://openjdk.java.net/jeps/261) - Reponse to largely changed file paths caused by [JEP 220](https://openjdk.java.net/jeps/220). - Modifications in build system related to AdoptOpenJDK and Java 11 which have a different naming structure for downloads. - Allowing use of non-Oracle Java within internal Processing checks. **Secondary required changes:** There were some secondary required changes that impacted the usability of Processing after having moved to OpenJFX / OpenJDK 11: - Removal of com.apple.eawt calls related to [JEP 272](http://openjdk.java.net/jeps/272) - Response to HiDPI support on Windows and Linux in [JEP 263](https://openjdk.java.net/jeps/263) - Removal of `java.ext.dirs`. Would be forced by [JEP 220](http://openjdk.java.net/jeps/220). - Due to bugs on Windows, updated the JNA jars. - Changes in downloader build tasks to support AdoptOpenJDK and OpenJFX. - Updated org.eclipse.* / equinox jars. - Some optimization around size of distribution. - Update of AppBundler. - Some changes in formulation of classpath and modifications in PreprocessingService given [JEP 261](https://openjdk.java.net/jeps/261). **Incidental changes:** This was (ahem) a bit of a larger PR with the above modifications. So, I wanted to introduce automated tests when possible and convenient along with a few changes for platform sustainability in order to support development: - Addition of cross-building capability (!) made possible by AdoptOpenJDK. - Addition of mockito for testing. - Upgrade of junit. - Addition of ant-contrib. - Standardized nomenclature around JRE / JDK in `build/build.xml` - Deduplication of code in `jre/build.xml`. - Addition of JavaDoc in a few places. - Some refactoring of PImage / Shape to support increased testing and readability in image manipulation code.
42 lines
1.9 KiB
HTML
42 lines
1.9 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
|
|
<title>About</title>
|
|
</head>
|
|
<body lang="EN-US">
|
|
<h2>About This Content</h2>
|
|
|
|
<p>November 30, 2017</p>
|
|
<h3>License</h3>
|
|
|
|
<p>
|
|
The Eclipse Foundation makes available all content in this plug-in
|
|
("Content"). Unless otherwise indicated below, the Content
|
|
is provided to you under the terms and conditions of the Eclipse
|
|
Public License Version 2.0 ("EPL"). A copy of the EPL is
|
|
available at <a href="http://www.eclipse.org/legal/epl-2.0">http://www.eclipse.org/legal/epl-2.0</a>.
|
|
For purposes of the EPL, "Program" will mean the Content.
|
|
</p>
|
|
|
|
<p>
|
|
If you did not receive this Content directly from the Eclipse
|
|
Foundation, the Content is being redistributed by another party
|
|
("Redistributor") and different terms and conditions may
|
|
apply to your use of any object code in the Content. Check the
|
|
Redistributor's license that was provided with the Content. If no such
|
|
license exists, contact the Redistributor. Unless otherwise indicated
|
|
below, the terms and conditions of the EPL still apply to any source
|
|
code in the Content and such source code may be obtained at <a
|
|
href="http://www.eclipse.org/">http://www.eclipse.org</a>.
|
|
</p>
|
|
|
|
|
|
<h3>Disassembler</h3>
|
|
<p>This plug-in contains a bytecode disassembler ("Disassembler") that can produce a listing of the Java assembler mnemonics ("Assembler Mnemonics") for a Java method. If you
|
|
use the Disassembler to view the Assembler Mnemonics for a method, you should ensure that doing so will not violate the terms of any licenses that apply to your use of that method, as
|
|
such licenses may not permit you to reverse engineer, decompile, or disassemble method bytecodes.</p>
|
|
|
|
</body>
|
|
</html> |