Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » TMF (Xtext) » Single project for Xtext
Single project for Xtext [message #1162735] Wed, 30 October 2013 15:32 Go to next message
Andrew Gacek is currently offline Andrew GacekFriend
Messages: 32
Registered: October 2011
Member
I'd like to put both of my xtext projects (mydsl and mydsl.ui) in to the same project. I can update the mwe2 as follows

    component = Generator {
    	pathRtProject = runtimeProject
    	pathUiProject = runtimeProject    	
    	projectNameRt = projectName
    	projectNameUi = projectName


I've moved over my custom source files from the ui project to the runtime project, and I've merged the plugin.xml file. Everything seems to be working fine, but I get three warnings:

Description	Resource	Path	Location	Type
Referenced identifier 'org.xtext.example.mydsl.ui.mydsl.check.expensive' in attribute 'markerType' cannot be found	plugin.xml	/org.xtext.example.mydsl	line 345	Plug-in Problem
Description	Resource	Path	Location	Type
Referenced identifier 'org.xtext.example.mydsl.ui.mydsl.check.fast' in attribute 'markerType' cannot be found	plugin.xml	/org.xtext.example.mydsl	line 329	Plug-in Problem
Description	Resource	Path	Location	Type
Referenced identifier 'org.xtext.example.mydsl.ui.mydsl.check.normal' in attribute 'markerType' cannot be found	plugin.xml	/org.xtext.example.mydsl	line 337	Plug-in Problem


I've tried fixing these manually, but even when I get the ids to match the declared check ids, it still gives the warning. Is there something else I have to do?

In general, is there any strong reason why I should not merge the runtime and the ui project, if I only ever intend to use them together?

Thanks,
Andrew
Re: Single project for Xtext [message #1162743 is a reply to message #1162735] Wed, 30 October 2013 15:38 Go to previous messageGo to next message
Andrew Gacek is currently offline Andrew GacekFriend
Messages: 32
Registered: October 2011
Member
I was able to fix the markerType warnings by dropping only the 'ui' part of the markerType reference. So now I have ones like
org.xtext.example.mydsl.mydsl.check.fast

I did understand before exactly how these names were formed, but now it makes sense.

So the only question I have left is if there is a strong reason not to put the runtime and ui project together.
Re: Single project for Xtext [message #1170020 is a reply to message #1162743] Mon, 04 November 2013 10:51 Go to previous message
Axel Guckelsberger is currently offline Axel GuckelsbergerFriend
Messages: 347
Registered: July 2009
Senior Member
If you keep UI dependencies separated it is easier to build your plug-ins
headlessly and/or execute tests for them.
Beside that 'separation of concerns' is a basic principle in software
development. So at the end unifying both projects makes things more complex
instead of simplifying them.


Andrew Gacek wrote:

> I was able to fix the markerType warnings by dropping only the 'ui' part
> of the markerType reference. So now I have ones like
> org.xtext.example.mydsl.mydsl.check.fast I did understand before exactly
> how these names were formed, but now it makes sense.
>
> So the only question I have left is if there is a strong reason not to put
> the runtime and ui project together.
Previous Topic:endless Loop with extern lexer
Next Topic:Resolving correct inferred variable
Goto Forum:
  


Current Time: Mon Nov 30 08:52:50 GMT 2020

Powered by FUDForum. Page generated in 0.01469 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top