Re: [cross-project-issues-dev] Errors when running 2018-12 RC2 on Java 1

[Holger Voormann <eclipse@xxxxxxxxxxx>]

Hi Ed,

As already mentioned, the Java EE package is not affected (see 
https://www.eclipse.org/lists/cross-project-issues-dev/msg16292.html):

Currently (2018-12 RC2), when one of the following Eclipse IDE package 
is run on Java 11 the "Report Bug or Enhancement" and the "Task Search" 
features are broken and 82 lines are added to the log each time the IDE 
is started:
- Eclipse IDE for Java Developers
- Eclipse IDE for Eclipse Committers
- Eclipse IDE for JavaScript and Web Developers
- ... (probably more IDE packages whithout the "javax.xml.bind" plugin)

Not affected are the C/C++, PHP, Rust and Jave EE packages containing 
"javax.xml.bind" via a different dependency than the Mylyn Bugzilla 
connector.

Regards,

Holger

Am 18.12.2018 um 09:44 schrieb Ed Merks:
> Mickael,
>
> 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:
>
> eclipse.buildId=4.10.0.I20181121-1800
> java.version=11.0.1
> java.vendor=Oracle Corporation
> 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 
> org.eclipse.epp.package.jee.product
>
> org.eclipse.jface.text
> Warning
> Tue Dec 18 09:35:17 CET 2018
> Duplicate template id: 'org.eclipse.wst.xslt.templates.xpath.boolean'
>
> 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 this point.
>
> Regards,
> Ed
>
> On 18.12.2018 09:17, Mickael Istria wrote:
> > Hi,
> >
> > 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 whole SimRel.
> >
> > My 2c.
> >
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev