I installed the 2022-09 PHP package and it came up free of errors
in the log. I also visited all the preference pages and only
this warning was logged:
org.eclipse.ptp.rm.lml.monitor.core
Info
Fri Sep 02 08:53:18 CEST 2022
D:\Users\test17\eclipse-workspace-parallel\.metadata\.plugins\org.eclipse.ptp.rm.lml.monitor.core\monitors.xml
(The system cannot find the file specified)
org.eclipse.linuxtools.rpm.rpmlint
Warning
Fri Sep 02 08:53:19 CEST 2022
The preference page RPM -> Rpmlint comes up in an invalid state
The IDE seems to go into an infinite (more than 1 hour so far)
Update RPM packages proposal list once started; I think the
visiting of the preference triggered that.
I could create a C/C++ project but I didn't know how to complete
the paths to the tools so that caused errors.
org.eclipse.cdt.core
Error
Fri Sep 02 08:59:14 CEST 2022
Error: Cannot run program "gcc": Launching failed
java.io.IOException: Cannot run program "gcc": Launching failed
at
org.eclipse.cdt.utils.spawner.Spawner.exec(Spawner.java:450)
at
org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:147)
at
org.eclipse.cdt.utils.spawner.Spawner.<init>(Spawner.java:134)
at
org.eclipse.cdt.utils.spawner.ProcessFactory.exec(ProcessFactory.java:131)
at
org.eclipse.cdt.core.CommandLauncher.execute(CommandLauncher.java:190)
at
org.eclipse.cdt.internal.core.BuildRunnerHelper.build(BuildRunnerHelper.java:274)
at
org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.runProgramForLanguage(AbstractBuiltinSpecsDetector.java:799)
at
org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.runForLanguage(AbstractBuiltinSpecsDetector.java:727)
at
org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.runForEachLanguage(AbstractBuiltinSpecsDetector.java:592)
at
org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector$1.runInWorkspace(AbstractBuiltinSpecsDetector.java:518)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:43)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
_____________________________________________
The Modeling package also came up without warnings and no issue
logged visiting the preferences. I could create a modeling
project and edit a diagram without problems.
______________________________________________
I tested the Committers package using it to create an EPP
development environment. That all works well except for this long
standing warning about conflicting key bindings:
org.eclipse.emf.parsley
Error
Fri Sep 02 09:37:27 CEST 2022
FrameworkEvent ERROR
org.osgi.framework.BundleException: Could not resolve module:
org.eclipse.emf.parsley [892]
Unresolved requirement: Require-Bundle:
org.eclipse.emf.parsley.runtime; visibility:="reexport"
-> Bundle-SymbolicName: org.eclipse.emf.parsley.runtime;
bundle-version="1.13.0.v20201130-1005"
org.eclipse.emf.parsley.runtime [905]
No resolution report for the bundle. Unresolved
requirement: Require-Bundle: org.eclipse.emf.parsley.common;
visibility:="reexport"
-> Bundle-SymbolicName: org.eclipse.emf.parsley.common;
bundle-version="1.13.0.v20201130-1005"; singleton:="true"
org.eclipse.emf.parsley.common [895]
No resolution report for the bundle. Bundle was not
resolved because of a uses constraint violation.
org.apache.felix.resolver.reason.ReasonException: Uses
constraint violation. Unable to resolve resource
org.eclipse.emf.parsley [osgi.identity;
osgi.identity="org.eclipse.emf.parsley"; type="osgi.bundle";
version:Version="1.13.0.v20201130-1005"; singleton:="true"]
because it is exposed to package 'com.google.common.base' from
resources com.google.guava [osgi.identity;
osgi.identity="com.google.guava"; type="osgi.bundle";
version:Version="31.1.0.jre"] and com.google.guava [osgi.identity;
osgi.identity="com.google.guava"; type="osgi.bundle";
version:Version="30.1.0.v20210127-2300"] via two dependency
chains.
Chain 2:
org.eclipse.emf.parsley [osgi.identity;
osgi.identity="org.eclipse.emf.parsley"; type="osgi.bundle";
version:Version="1.13.0.v20201130-1005"; singleton:="true"]
require: (osgi.wiring.bundle=org.eclipse.emf.parsley.runtime)
|
provide: osgi.wiring.bundle;
bundle-version:Version="1.13.0.v20201130-1005";
osgi.wiring.bundle="org.eclipse.emf.parsley.runtime"
com.google.inject [osgi.identity;
osgi.identity="com.google.inject"; type="osgi.bundle";
version:Version="5.0.1.v20210324-2015"]
import:
(&(osgi.wiring.package=com.google.common.collect)(&(version>=30.1.0)(!(version>=31.0.0))))
|
export: osgi.wiring.package: com.google.common.collect;
uses:=com.google.common.base
export: osgi.wiring.package=com.google.common.base
com.google.guava [osgi.identity;
osgi.identity="com.google.guava"; type="osgi.bundle";
version:Version="30.1.0.v20210127-2300"]
at org.eclipse.osgi.container.Module.start(Module.java:463)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852)
at
org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1786)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672)
at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
Hopefully no one will try to install both WindowBuilder and
Parsley.
This free-for-all anyone can pull anything directly from Maven
makes coordinating versions more challenging. This is especially
bad for libraries such as Guava that are often surfaced in the
APIs...
Regards,
Ed
On 01.09.2022 23:34, Jonah Graham
wrote:
Hi everyone,
Our next milestone build is available for testing: EPP 2022-09
RC1
A couple of concerns:
Bugzilla links in descriptions
some packages (committers, jee, php) have descriptions in
the epp.website.xml file that refer to Bugzilla for filing
bugs for Eclipse Platform. Can the package maintainers
please review the descriptions ahead of RC2 next week? Here
is an example of what it looks like generated.
Note that I will make the trivial change of changing the
Eclipse Platform link and see if I can get the older
releases fixed too because as of today https://www.eclipse.org/downloads/packages/
has links that leads to errors like this:
Untested/unreported packages
parallel and php have not had a test report back in
some time.
Please test and send your +1 to this mailing list. +1s are
optional as the package will be published anyway.
Last +1 received for each package and platform (apologies if
I missed one of your +1 emails, just let me know and I will
update Last Recorded +1) I have highlighted those
packages/platforms that I haven't seen any confirmation in
this release cycle on.