I installed the Java EE package just now with the Eclipse
Installer (which installed RC1 until RC2/R is actually visible)
choosing a Java 11 JDK and I see nothing worrisome in the Error
log initially, other than the usual EGit warning about HOME not
being set and the following unproblematic warning:
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product
Tue Dec 18 09:35:17 CET 2018
Duplicate template id:
Of course I expect that package testers would inspect the Error
log for problems...
This isn't to say that once you start using the package to do
real things, that some problem doesn't show up but even trying to
create some projects I didn't see anything in the Error log.
But note that this test uses the product catalog generated for
RC2, which has removed the Recommender features and one Mylyn
feature, so perhaps that's why I don't see any logged problems at
On 18.12.2018 09:17, Mickael Istria
Is the issue surfacing for end-users who have Mylyn
installed but not used? Is it blocking further usage or just
making Mylyn feature fail? Is the failure hard and ugly or is
it some error pop-up, or an error view or a log entry when
trying to use a bugged feature...?
I think if it's only affecting Mylyn, not cascading to
other workflows/components and only on Java 11, the amount of
users who're using Java 11 and Mylyn simultaneously should be
low enough to make it acceptable to ship it as it anyway
without respinning or delaying anything.
And if we need to respin something, we could consider just
removing Mylyn from EPP packages instead of rebuilding the
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit