Eclipse Community Forums: TMF (Xtext) » discouraged access to org.eclipse.xtext.ui.wizard.template contents

Help

Home

Home » Modeling » TMF (Xtext) » discouraged access to org.eclipse.xtext.ui.wizard.template contents

Show: Today's Messages :: Show Polls :: Message Navigator

discouraged access to org.eclipse.xtext.ui.wizard.template contents [message #1839883]

Wed, 31 March 2021 06:52

Volker Wegert

Messages: 182
Registered: July 2009

Senior Member

Hi all,

The generated template provider classes contain references to various interfaces in org.eclipse.xtext.ui.wizard.template - namely

import org.eclipse.xtext.ui.wizard.template.FileTemplate
import org.eclipse.xtext.ui.wizard.template.IFileGenerator
import org.eclipse.xtext.ui.wizard.template.IFileTemplateProvider
import org.eclipse.xtext.ui.wizard.template.IProjectGenerator
import org.eclipse.xtext.ui.wizard.template.IProjectTemplateProvider
import org.eclipse.xtext.ui.wizard.template.ProjectTemplate

This causes a number of warnings in the IDE because the package is not among those exported by org.eclipse.xtext.ui. Is this a bug or did I miss something...?

Xtext Complete SDK 2.25.0.v20210301-1429

Thanks
Volker

Report message to a moderator

Re: discouraged access to org.eclipse.xtext.ui.wizard.template contents [message #1839885 is a reply to message #1839883]

Wed, 31 March 2021 06:59

Christian Dietrich

Messages: 14665
Registered: July 2009

Senior Member

alll these files are also marked as @Beta
please create an issue at https://github.com/eclipse/xtext-eclipse to discuss

Twitter : @chrdietrich
Blog : https://www.dietrich-it.de

[Updated on: Wed, 31 March 2021 07:02]

Report message to a moderator

Re: discouraged access to org.eclipse.xtext.ui.wizard.template contents [message #1839888 is a reply to message #1839885]

Wed, 31 March 2021 07:19

Tamas Miklossy

Messages: 157
Registered: February 2016

Senior Member

Hello Volker,

As a workaround you can supress the warnings by defining explicit access rules for classes or packages in the Library section of the Build Path settings:
open "Plug-in Dependencies" and Edit on Access Rules. Add a rule of type "Accessible". Note that you have to convert a class name to a path with "/".

Hope that helps,
Tamás

Report message to a moderator