On windows the generated classpath in start scripts might become too
long. This can be avoided by additional configuration of the
appassembler-maven-plugin plugin:
- added option repositoryLayout=flat
- added option useWildcardClassPath=true
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
The IDE project's build can be extended to create an executable Language
Server. The Language Server can be configured to be built either as a
distribution with seperate jars or as a fat jar.
Due to a limitation of the maven-shade-plugin in a Maven/Tycho
environment the build must be tweaked a bit to materialize dependencies
with the maven-dependencies-plugin and attached for inclusion with the
addjars-maven-plugin.
Extended the test suite for the different configurations with language
server support:
- plain Maven
- Maven/Tycho
- Gradle
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
The IDE project's build can be extended to create an executable Language
Server. The Language Server can be configured to be built either as a
distribution with seperate jars or as a fat jar.
Due to a limitation of the maven-shade-plugin in a Maven/Tycho
environment the build must be tweaked a bit to materialize dependencies
with the maven-dependencies-plugin and attached for inclusion with the
addjars-maven-plugin.
Extended the test suite for the different configurations with language
server support:
- plain Maven
- Maven/Tycho
- Gradle
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
The IDE project's build can be extended to create an executable Language
Server. The Language Server can be configured to be built either as a
distribution with seperate jars or as a fat jar.
Due to a limitation of the maven-shade-plugin in a Maven/Tycho
environment the build must be tweaked a bit to materialize dependencies
with the maven-dependencies-plugin and attached for inclusion with the
addjars-maven-plugin.
Extended the test suite for the different configurations with language
server support:
- plain Maven
- Maven/Tycho
- Gradle
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
* consolidated version of 'org.junit' with our reference in 'gradle/versions.gradle' (currently 4.12)
* added dependency to 'junit:junit:4.12' with scope 'testCompile' to templates of 'pom.xml' + 'build.gradle'
Signed-off-by: Christian Schneider <christian.schneider@typefox.io>
The Xtend compiler was optimized to minimize the usage of synthetic variables for member feature calls and right-hand assignments
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
For comparison with null the triple (not) equal operator should be used.
Resolved compiler warnings
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
For comparison with null the triple (not) equal operator should be used. Resolved compiler warnings
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
see https://github.com/eclipse/xtext-umbrella/issues/3
Remove org.eclipse.buildship.core.prefs
Files are generated on Gradle project import or by Oomph setup
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
connection.project.dir changed to composite build location in new
umbrella project
value 'containers' added by Buildship
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
Add 'lineDelimiter' to project configuration and generate it to the
'code' configuration in the workflow.
Adjusted test expectations.
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
- Launch config for Runtime Eclipse is only generated when the runtime
project is a plugin project.
- Launch config for Xtext workflow is dependent on the build system. For
plain Maven projects the launch config uses the m2e launcher, for Gradle
builds buildship is launched.
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
- the runtime project excludes .mwe2 and .xtend files
- the feature sdk project excludes nothing
- all other Eclipse projects exclude .xtend
- add test case WizardConfigurationTest#binExcludes
Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
