| Re: [mat-dev] Next release of Memory Analyzer for Eclipse 2022-06 |
|
With the fix for help, I’ve done a
so the files are now at
https://download.eclipse.org/mat/1.13.0/ The MAT 1.13.0.202204291409 available from Eclipse 2022-06 doesn’t reference the /mat/latest update site so I don’t think there will be any problem with releasing 1.13.0.202206151457
as the standalone version. They should be functionally identical, and with Java 17 help should work with 1.13.0.202204291409 in Eclipse 2022-06 provided JDT is installed, and works with 1.13.0.202206151457 standalone. We haven’t decided on a date for a next
MAT release, and more people will be using Java 17 over the next few months, so working help is important. I’ll update the MAT website with the new download links assuming the downloads look okay. Andrew Johnson From: mat-dev <mat-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Grigorenko In my opinion, if it’s only broken for Java 17 and we haven’t received any complaints for this on MAT 1.12, then I don’t think it’s worth the effort as we can just suggest people use Java 11 until
MAT 1.14. -- Kevin Grigorenko IBM App Platform SWAT From:
mat-dev <mat-dev-bounces@xxxxxxxxxxx> on behalf of Andrew Johnson <andrew_johnson@xxxxxxxxxx> It’s not quite as straightforward for the 1.13.0 release. I made the change and the snapshot build looks good, and the help works with Java 17 (tested on Windows). However the mat-standalone-packages build is designed to take as the input the repo we used for the Eclipse simultaneous release, so for 2022-06 is download.eclipse.org/mat/2022-06/M2/ This has the plugins, and the features, including org.eclipse.mat.ui.rcp.feature_1.13.0.202204291409.jar which is the previous version without the mention of org.eclipse.jdt.core This means that when mat-standalone-packages builds the zips then org.eclipse.jdt.core is not included, and the help problem occurs with Java 17. So we could copy the latest snapshot build to download.eclipse.org/mat/2022-06/standalone/ (to keep it somewhere), and then do a mat-standalone-packages build from there, but the standalone build
would then have different dates from the simultaneous release version. The code in /mat/latest/update-site and /mat/1.13.0/update-site would then be later than the code in the main Eclipse site, /releases/2022-06 Would that matter? It’s possible that after
installing MAT into Eclipse from /releases/2022-06 that MAT would then see a later version in /mat/latest/update-site which would be offered as an update. Options:
Andrew Johnson From: mat-dev <mat-dev-bounces@xxxxxxxxxxx>
On Behalf Of Kevin Grigorenko If the solution is just the extra org.eclipse.jdt.core dependency, then that seems reasonable. Some users run MAT on intranets without internet access and I have seen them use help contents in
some cases and in that case, the workaround of “Install New Software } Eclipse 2022-03 } Eclipse Java Development Tools” won’t work (unless they download an offline update site for that which isn’t easy). -- Kevin Grigorenko IBM App Platform SWAT From:
mat-dev <mat-dev-bounces@xxxxxxxxxxx> on behalf of Andrew Johnson <andrew_johnson@xxxxxxxxxx> I have been preparing for the release, following
https://wiki.eclipse.org/MemoryAnalyzer/Contributor_Reference#Simultaneous_release_policies I have tagged the source and run the standalone packaging build and added 1.13 as a version to Bugzilla I have now found a problem with the standalone version (not a problem for MAT installed into Eclipse). 580157: Help fails with HTTP ERROR 500 org.apache.jasper.JasperException: PWC6033 with Java 17 https://bugs.eclipse.org/bugs/show_bug.cgi?id=580157 This problem also occurs with MAT 1.12.0 and Java 17, but no one has reported it over the past year. Do we live with this problem, caused by the following, or attempted to work around it by “-
a workaround: you should add the org.eclipse.jdt.core as a dependency to your project. (yes, it's an extra 7MB)”. I think it is just a case of adding the plugin to org.eclipse.mat.ui.rcp.feature/feature.xml
https://bugs.eclipse.org/bugs/show_bug.cgi?id=574937 578221: HTTP ERROR 500 org.apache.jasper.JasperException: PWC6033: Error in Javac compilation for JSP PWC6197: An error occurred at line: 41 in the jsp file: /index.jsp PWC6199: Generated servlet
error: System cannot be resolved https://bugs.eclipse.org/bugs/show_bug.cgi?id=578221 The release review is ongoing:
https://projects.eclipse.org/projects/tools.mat/reviews/1.13.0-release-review Andrew Johnson Unless otherwise stated above: Unless otherwise stated above:
Unless otherwise stated above:
IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU |