Hi Holger,
According to Lakshmi, there will be no Marketplace entry "Java 20
Support for Eclipse 2023-03 (4.27)" at the time of the 2023-03 release,
but maybe later. I’m concerned that JDK is that badly understaffed.
Looks like there is a misunderstanding.
Java 20 will be released only on March 21, after Eclipse release (on
March 15), so the market place entry it would come only after the release.
AFAIK this has been the case always, support for latest Java on
Marketplace is available only after its release.
Thanks,
Lakshmi
*From: *ide-dev <ide-dev-bounces@xxxxxxxxxxx> on behalf of Holger
Voormann <eclipse@xxxxxxxxxxx>
*Date: *Monday, 6 March 2023 at 10:30 PM
*To: *ide-dev@xxxxxxxxxxx <ide-dev@xxxxxxxxxxx>
*Subject: *[EXTERNAL] Re: [ide-dev] Highlights for 2023-03 landing page
Hi Andrey, hi all,
There are two questions:
- What are the six highlights of the Eclipse IDE 2023-03 release to be
shown at eclipseide.org?
- Which Eclipse Java IDE 2023-03 improvements should I show in my next
video?
In 2023-03 there are not that many new features. The Bytcode view you
contributed to JDT (many thanks for that!) is one of the few new
features. But the Bytcode view is included in the SDK only, so I think
it would be misleading to call it a new Eclipse IDE(!) highlight as long
as the Bytecode view is not part of the Java IDE packages.
Should I show the Bytecode view in my video? If so, an explanation of
how to get it would be probably necessary, but then one would wonder why
it is not included. I’m not sure, but I think it is better not to show
the Bytecode view in my video when it is not included in the Java IDE
packages.
I would love to have the Bytecode view in all Java IDE packages (still
hoping it’s not too late for 2023-03): https://eclip.se/581619
<https://eclip.se/581619>
According to Lakshmi, there will be no Marketplace entry "Java 20
Support for Eclipse 2023-03 (4.27)" at the time of the 2023-03 release,
but maybe later. I’m concerned that JDK is that badly understaffed.
My main focus is creating the video, but I do my best to give my input
to the landing page and report issues I find while testing the new
features. In the meantime, I tested almost all the new features of the
Java IDE 2023-03. I hope I have not overlooked anything important:
https://github.com/howlger/Eclipse-IDE-improvements-videos#features-to-show <https://github.com/howlger/Eclipse-IDE-improvements-videos#features-to-show>
New issue found (maybe only on Windows 11 with a fresh workspace, but
makes Alt+Shift+R unusable and looks bad):
https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/443
<https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/443>
I could not reproduce the JGit performance improvement in EGit (in the
History view, I didn’t notice any performance differences with and
without the commit-graph for the Linux Git repositories). But I see a
significant speedup by the Java compiler, probably due to or mainly due to
https://github.com/eclipse-jdt/eclipse.jdt.core/issues/549
<https://github.com/eclipse-jdt/eclipse.jdt.core/issues/549>
Wouldn’t that be worth mentioning as well?
How about linking the six highlights of the landing page to the
corresponding project "New and Noteworthy" item? It would be a bit more
work, but maybe worth it to somewhat compensate for the lack of an
aggregated "New and Noteworthy" list?
Thanks,
Holger
Am 02.03.2023 um 16:25 schrieb Andrey Loskutov:
See my answers inline to questions where I can something contribute.
On Thursday March 2 15:36:11 2023 (+01:00), Holger Voormann wrote:
The "Bytecode" view (and for details, the "Bytecode Reference" view)
is useful for Java developers in general to get an insight into the
bytecode, whereas the AST view (and for details, the "Element" view)
is only useful when developing something using the Eclipse compiler
for Java (ecj) as dependency, right?
Almost. AST/Element views are useful for JDT core developers (ecj is a subset of JDT core).
I would like to see the "Bytecode" view included in all Java IDE
packages.
If you want it to be in other packages, open tickets for the package maintainers.
Otherwise, it should not be mentioned on the Eclipse IDE
web site.
If the mention on the site includes hint how to install, IMHO that's enough, but I have no preference here.
The "AST" view should also be able to be installed with
"Group items by category".
Who needs that? JDT developers get the tool for free via SDK, others most likely don't want that anyway.
It might be mentioned together with
"ECJ separated from JDT Core" [5]
It is completely unrelated to ecj separation from JDT core.
Ecj separation from JDT core means in short that ecj is a *real* bundle now, that can be used as a full featured Java compiler inside IDE that does NOT have entire JDT tooling installed.
(by the way, does this mean that
ecj is now available as a single dependency from Maven Central and
if so, which one?).
It was there before, and is still under same id.
As of today, 4.26 version is https://central.sonatype.com/artifact/org.eclipse.jdt/ecj/3.32.0
<https://central.sonatype.com/artifact/org.eclipse.jdt/ecj/3.32.0>
- There should no "Javadoc: Missing tag for return type" for
"{@return ...}" [16]
IMHO as long as this is not implemented, inline @return
should not mentioned [17].
Well, bugs exist in every software.
May be the one who cares and sees the warning would be triggered by this feature mentioned and would contribute a patch?
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ide-dev
<https://www.eclipse.org/mailman/listinfo/ide-dev>
