Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Compilation Errors in Papyrus Neon Workspace

Hi Christian,

 

I’ve had most of these issues as well, and fixed a few (Although sometimes in separate branches that are not merged yet). Some info:

 

Ø  The method getAdapter(Object, Class<T>, T) is ambiguous for the type PlatformHelper ComponentPart.java 

I think the adapter API has been recently augmented with generics and Java 8 constructs, causing a new ambiguity. Tycho doesn’t complain, so this might be a bug in the JDT Compiler? The ambiguity can be solved with an explicit cast

 

Ø  The method or field failing is undefined    ClassDiagramGenerateTestsWorkflow.xtend

I’m not using the test generator in my workspace, so I didn’t have this error

 

Ø  no viable alternative at input ';'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 237

 

Some regressions have been introduced via Bug 493257 [1]. I pushed a fix yesterday, and also added the XText nature to this project, so now XText tries to compile this file. I will check this on the latest nightly, but there are 2 possibilities:

 

-          You’re not entirely up-to-date in your installed platform (Commit 9243d63)

-          Something’s wrong with either the CSS Grammar or this CSS File (Or both)

 

Ø  Bundle org.eclipse.papyrus.uml.diagram.paletteconfiguration.editor:

Ø  and it looks like this project has no code nor manifest?

 

I’ve noticed that as well; I don’t know the status of palette configuration. Mickaël is working on the new XMI Palette Editor to replace the XML one, so maybe this bundle was supposed to be deleted?

 

Ø  Bundle org.eclipse.papyrus.releng.tools:

 

This one has an optional dependency to the *.tpd project. I didn’t add an explicit dependency because we don’t have a CQ for that, and it’s only a developer tool. So the plug-in needs to be installed manually (if you ever need it – that’s not mandatory if you’re not updating the Target Platforms). More info about this tool here [2]

 

Ø  In bundle org.eclipse.papyrus.uml.ui.perspectiveconfiguration:

 

This bundle is not built and should be deleted

 

[1] 493257: [CSS] Formatter stop working on some cases

https://bugs.eclipse.org/bugs/show_bug.cgi?id=493257

 

[2] https://dev.eclipse.org/mhonarc/lists/mdt-papyrus.dev/msg03361.html

 

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian Damus
Envoyé : mercredi 25 mai 2016 02:35
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] Compilation Errors in Papyrus Neon Workspace

 

Hi,

It’s been a couple of weeks since I worked in my Papyrus development workspace (having been focused on Papyrus-RT), and now I find I’m quite out of touch and have compilation errors all over the place. I pulled the latest from git today and ran the Oomph setup to get all of the latest target platform. I have these errors:

Bundle org.eclipse.papyrus.infra.core.sasheditor:

The method getAdapter(Object, Class<T>, T) is ambiguous for the type PlatformHelper ComponentPart.java  /org.eclipse.papyrus.infra.core.sasheditor/src/org/eclipse/papyrus/infra/core/sasheditor/internal   line 65 Java Problem
The target type of this _expression_ must be a functional interface   ComponentPart.java  /org.eclipse.papyrus.infra.core.sasheditor/src/org/eclipse/papyrus/infra/core/sasheditor/internal   line 65 Java Problem
The target type of this _expression_ must be a functional interface   EditorPart.java /org.eclipse.papyrus.infra.core.sasheditor/src/org/eclipse/papyrus/infra/core/sasheditor/internal   line 179    Java Problem

Bundle org.eclipse.papyrus.uml.diagram.clazz.tests:

The method or field failing is undefined    ClassDiagramGenerateTestsWorkflow.xtend /org.eclipse.papyrus.uml.diagram.clazz.tests/test/org/eclipse/papyrus/uml/diagram/clazz/tests/generation    line: 70 /org.eclipse.papyrus.uml.diagram.clazz.tests/test/org/eclipse/papyrus/uml/diagram/clazz/tests/generation/ClassDiagramGenerateTestsWorkflow.xtend   Xtend Problem
The method or field failing is undefined    ClassDiagramGenerateTestsWorkflow.xtend /org.eclipse.papyrus.uml.diagram.clazz.tests/test/org/eclipse/papyrus/uml/diagram/clazz/tests/generation    line: 94 /org.eclipse.papyrus.uml.diagram.clazz.tests/test/org/eclipse/papyrus/uml/diagram/clazz/tests/generation/ClassDiagramGenerateTestsWorkflow.xtend   Xtend Problem

Similar problems in other UML diagram test bundles.

Bundle org.eclipse.papyrus.uml.diagram.css:

no viable alternative at input ';'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 237 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css    CSS Problem
no viable alternative at input ';'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 237 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css    CSS Problem
no viable alternative at input ';'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 28 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css CSS Problem
no viable alternative at input ';'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 28 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css CSS Problem
no viable alternative at input '*'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 236 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css    CSS Problem
no viable alternative at input '*'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 236 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css    CSS Problem
no viable alternative at input '*'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 236 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css    CSS Problem
no viable alternative at input '*'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 236 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css    CSS Problem
no viable alternative at input '*'  umlBase.css /org.eclipse.papyrus.uml.diagram.css/theme  line: 236 /org.eclipse.papyrus.uml.diagram.css/theme/umlBase.css    CSS Problem

and lots more CSS problems like these.

Bundle org.eclipse.papyrus.uml.diagram.paletteconfiguration.editor:

Attribute 'id' of element 'plugin' must be defined. plugin.xml  /org.eclipse.papyrus.uml.diagram.paletteconfiguration.editor    line 7  Plug-in Problem
Attribute 'name' of element 'plugin' must be defined.   plugin.xml  /org.eclipse.papyrus.uml.diagram.paletteconfiguration.editor    line 7  Plug-in Problem
Attribute 'version' of element 'plugin' must be defined.    plugin.xml  /org.eclipse.papyrus.uml.diagram.paletteconfiguration.editor    line 7  Plug-in Problem

and it looks like this project has no code nor manifest?

Bundle org.eclipse.papyrus.releng.tools:

Converter cannot be resolved to a type  GenerateTargetsHandler.java /org.eclipse.papyrus.releng.tools/src/org/eclipse/papyrus/releng/tools/internal/popup/actions   line 235    Java Problem
ICompositeNode cannot be resolved to a type TPDUpdater.java /org.eclipse.papyrus.releng.tools/src/org/eclipse/papyrus/releng/tools/internal/popup/actions   line 119    Java Problem
ILeafNode cannot be resolved to a type  TPDUpdater.java /org.eclipse.papyrus.releng.tools/src/org/eclipse/papyrus/releng/tools/internal/popup/actions   line 122    Java Problem

and more like this on missing packages fr.obeo.releng.targetplatform.*.

In bundle org.eclipse.papyrus.uml.ui.perspectiveconfiguration:

Bundle 'org.eclipse.papyrus.editor.perspectiveconfiguration' cannot be resolved MANIFEST.MF /org.eclipse.papyrus.uml.ui.perspectiveconfiguration/META-INF   line 2  Plug-in Problem
Unknown extension point: 'org.eclipse.papyrus.editor.perspectiveconfiguration'  plugin.xml  /org.eclipse.papyrus.uml.ui.perspectiveconfiguration    line 5  Plug-in Problem

Any suggestions how to fix these problems? I feel as though I must be missing something obvious. I see that the master branch builds don’t fail, so the root cause(s) is/are local, but running the Oomph setup doesn’t seem to resolve them.

Thanks,

Christian

 

 

 

 

Back to the top