JDK-8222778 : Packaging Tool (JEP 343) on Linux/AArch64
Type:Task
Component:tools
Sub-Component:jpackage
Affected Version:internal
Priority:P3
Status:Resolved
Resolution:Fixed
CPU:aarch64
Submitted:2019-04-19
Updated:2019-07-29
Resolved:2019-07-26
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
The jpackage implementation doesn't look cpu-specific, but dependent linux tools could have different command line options or behavior.
[This is a task for the aarch64 port.]
Proper deb arch detection in LinuxDebBundler
http://cr.openjdk.java.net/~dchuyko/8222778/webrev.04/
25-07-2019
Webrev modified according to comments, applies together with webrev.01 from JDK-8228402
http://cr.openjdk.java.net/~dchuyko/8222778/webrev.03/
24-07-2019
http://cr.openjdk.java.net/~dchuyko/8222778/webrev.00/
There is no cpu specific code, the fix was prepared and tested on: Linux x86_64, aarch64, x86, arm, power.
16-07-2019
JEP now targeted, so can target the implementation...
06-05-2019
There is some cpu-specific code in the implementation (mostly tests) in the latest patch: http://cr.openjdk.java.net/~herrick/8212780/webrev.ea6/open.patch
Look for "x86, i386, i486, i586, i686, amd64"
src/jdk.jpackage/share/classes/jdk/jpackage/internal/DeployParams.java:
* Has cpu code (see ���x86���), but aarch64 may work as-is?
src/jdk.jpackage/linux/classes/jdk/jpackage/internal/LinuxDebBundler.java
* This code looks wrong for aarch64 (see "i386").
test/jdk/tools/jpackage/createinstaller/linux/base/JPackageCreateInstallerBase.java ?
* See code like: "OUTPUT = "output" + File.separator + BUNDLE_NAME + "-1.0-1.x86_64." + EXT;"
test/jdk/tools/jpackage/createinstaller/linux/rpm/install.sh:
* ���sudo rpm --install jpackagecreateinstallerfileassociationstest-1.0-1.x86_64.rpm��� etc.
29-04-2019
+1. Also I recommend you to track the progress on CSR JDK-8213087 "CSR for JEP 343: Packaging Tool"
22-04-2019
Thanks Kevin, this is exactly what we are looking for!
22-04-2019
[~avoitylov] Andy will send out an updated webrev for code review in the next day or two. We do not expect any significant changes after that, so this might be a good starting point for your porting work (with the caveat you mentioned above about not being committed until all the reviews are done and the JEP is targeted).
22-04-2019
Vitya, thank you for making it symmetric and removing the fix version from the JEP.
Could you also have someone clarify the technical part of the question? What we are looking for is a notification when it is time for us to look into the porting/testing task. We are in no way looking for any commitment, just the technical details sufficient to proceed with the porting work.
22-04-2019
[~avoitylov] This feature will be targeted to the particular release per the JEP 2.0 process proposal [1]
...
Targeted ��� By the Project Lead, after evaluating the JEP���s engineering plan and seeing rough consensus amongst the Committers and Reviewers of the Project
...
[1] http://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
22-04-2019
~vdyakov JDK-8212780 has Fix Version 13. I don't have any reason to believe the porting/testing task should not be targeted to the same release.
What is missing on the technical side to have a good level of confidence that this work will land into JDK 13? We need this information to have this work ported/tested in the same release this work will land into.
22-04-2019
The JEP is not formally targeted (yet), so this is premature to target to "13"