Hi Marcel,
As I separated the project in o.e.r.templates and o.e.r.snipmatch.rcp I needed two workflow that would generate language artifacts. (one for o.e.r.templates.rcp and one for snipmatch.rcp)
In the build I included only the workflow for snipmatch.rcp, thus language artifacts were generated only for this project, not for o.e.r.templates.rcp. This leads to that error, as the project misses the generated sources.
For now I removed the o.e.r.templates.rcp and o.e.r.templates.tests from the build [1]. I will try to find a way (maybe create two profiles or two separate builds) to solve the issue and have a build for both the o.e.r.templates.rcp and o.e.r.snipmatch.rcp projects.
From: Marcel Bruch
Sent: Thursday, September 12, 2013 10:37 PM
To: Recommenders developer discussions
Hi Stefan,
Thanks for moving everything into master. I checked out your master branch and it looks much cleaner. Unfortunately, I've some trouble building your code. Running mvn clean install -Dlicense.failIfMissing=false fails with the errors below. How can these be fixed?
Thanks
Marcel
[ERROR]
ERROR: SnipDSLProposalProvider.xtend - /Users/Marcel/Repositories/SnipEditor/org.eclipse.recommenders.templates.rcp/src/org/eclipse/recommenders/templates/rcp/contentassist/SnipDSLProposalProvider.xtend
6: org.eclipse.recommenders.templates.rcp.contentassist.AbstractSnipDSLProposalProvider cannot be resolved to a type.
[ERROR]
ERROR: SnipDSLProposalProvider.xtend - /Users/Marcel/Repositories/SnipEditor/org.eclipse.recommenders.templates.rcp/src/org/eclipse/recommenders/templates/rcp/contentassist/SnipDSLProposalProvider.xtend
15: AbstractSnipDSLProposalProvider cannot be resolved to a type.
[ERROR]
ERROR: SnipDSLProposalProvider.xtend - /Users/Marcel/Repositories/SnipEditor/org.eclipse.recommenders.templates.rcp/src/org/eclipse/recommenders/templates/rcp/contentassist/SnipDSLProposalProvider.xtend
15: Superclass must be a class
Hi,
This is the weekly report for the snippet editor:
What was planned for this week:
-> try to compute types for elements like ${cursor} based on the context. e.g.: for the _expression_ if(${cursor}){}, ${cursor} should be treated as a Boolean.
-> try to add content assist to jFace variables like ${array}.
-> make the type section of the metadata page work properly and set up a nicer dialog to edit the fields in search patterns.
What was accomplished:
-> type computation has been set properly for all template variables. Although there might still be some issues ( I’m not sure I covered it all ) it should work fine.
-> content assist works for template variables. There still are some problems, as for the ${array} variable there are List proposals instead of Object[] proposals.
-> The types appear properly in the metadata page. There are all types that were computed, including the primitive ones.
-> A nicer pop-up text field editor is available for editing the search phrases.
What the plan is for the next week:
-> Correct the proposals for the ${array} variable.
-> Enable saving for the data in the metadata page.
-> Template expressions do not work fine with methods (I forgot to update the syntax for them to support template _expression_). For example, the method snippets (private method, private static method, etc) do not work and will cause errors.
_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/recommenders-dev
