| Mark errors in the builded with the ant and maven plugins which use xtext [message #1748023] |
Thu, 17 November 2016 15:55  |
Eclipse User |
|
|
|
I have group of the plug-ins builded with xtext technology. When I build site update via eclipse all of the syntax, or lexical, or other errors occurs emmidiately on the problems view as well as in the project structure tree
But, when I do the same with maven and ant I haven't any errors message on the problem view, the some with project tree view
Where can be problem?
Regards, Vladimir
|
|
|
|
|
|
|
|
|
|
|
| Re: Mark errors in the builded with the ant and maven plugins which use xtext [message #1748037 is a reply to message #1748035] |
Thu, 17 November 2016 17:15  |
| Eclipse User |
|
|
|
1. Do you have any warnings on any build.properties files?
Yes, I have for example for file
source.. = src/main/java/,\
src/main/resources/,
output.. = bin/
bin.includes = plugin.xml,\
META-INF/,\
.,\
icons/,\
target/dependency/jfxswt-8.0.jar
I have following warning
Quote:The folder "bin/" does not exist in the workspace
Can you share a reproducible example repro I can start the build from?
Unfortunatly not, as I have a lot of the projects so it's difficult to create reproducible snippet.
Maybe you know where I can set up showing problems in the error logging? Some "settings" file where I can disable, or enable showing errors in the "problems" view?
|
|
|
|
|
| Re: Mark errors in the builded with the ant and maven plugins which use xtext [message #1748040 is a reply to message #1748039] |
Thu, 17 November 2016 17:40 |
| Eclipse User |
|
|
|
Well I assume that the plugins you package miss half of the stuff.
This will lead to the Xtext framework no being properly configured
Open the jars files using unzip and look what is missing. Are all files there?
In your target eclipse you can open console view
And select host Osgi console on the little arrow
Then type ss yourpluginid or simply ss
This should give you a list of plugin ids states and a number
If the state of the plugin is not active you can start it by start <number of plugin>
This may give you an exception
Or you example remote debugging and debug the Xtext builder and clusting builder state classes
There is everything e.g. Building and marker creation
But again I strongly recommend you to create a maven Xtext project using the wizard
And compare the contents of the jar files and the behavior in eclipse
Ps do you test runtime and from update site eclipse with the same settings /projects
(Build automatically on, project has Xtext nature, file extension case sensitive, ....)
|
|
|
Powered by
FUDForum. Page generated in 0.04243 seconds
Home