first congratulations to the new release. I started migration yesterday, but fail to run the Maven build, because the final 2.11 version has not landed in Maven central yet.
This leads to the following error message:
Failed to collect dependencies at org.eclipse.xtext:xtext-maven-plugin:jar:2.11.0 -> org.eclipse.xtext:org.eclipse.xtext.builder.standalone:jar:[2.11.0]: No versions available for org.eclipse.xtext:org.eclipse.xtext.builder.standalone:jar:[2.11.0] within specified range
Was this update forgotten or does it just need some time?
As far as I know, the "xtext-gradle-plugin" does not currently support building Eclipse Plugins with Gradle. Therefore, I wrote my own gradle script for our continuous integration that builds the Eclipse Plugin without requiring a full Eclipse installation.
The required Xtext packages are fetched using the gradle dependency management. Also, we use the "xtext-gradle-plugin" for compiling xtend files.
I tried using the "com.diffplug.gradle.p2.asmaven" gradle plugin to get the packages directly from the official xtext release update site. But unfortunately I ran into some problems caused by the different version format ("2.11.0.v*" vs. "2.11.0").
So, my idea was to use the published Maven artifacts (that are not available for 2.11.0). Do you have any suggestions?
Manuel Das> I'm facing the same issue as we started our continous integration tool on xtext 2.9.2, which is the only version for which org.eclipse.xtext.builder is published on maven central; but I'm now stuck as we're updating to 2.13.
What was your final solution (I'm looking at p2asmaven too, but it's not straightforward) ?
Thanks for your answer Christian. I'm talking about the jar for org.eclipse.xtext.builder, whose only versions on maven central are 2.9.* and 2.10.0: see this search on maven central.
I need it, because we build a command line compiler for our custom xtext-based language (at http://www.provenrun.com), which doesn't require a UI Eclipse to be available; but nevertheless depends on features of Eclipse that can be used without osgi running (IProgressMonitor, IPath, etc.).
I see, we depend on org.eclipse.xtext.builder for example because there's a single xtext builder for the core (headless) plugin and the UI plugin; and it needs to implement org.eclipse.xtext.builder.IXtextParticipant for the latter (and this interface is fine for being used without osgi running). I'll investigate how far our dependency goes and better split the core and the UI plugin to see if I can get rid of this dependency. Our distinction between core and UI was made circa 2013 and it hasn't changed much since, so we should update on this topic.
Yes we go headless and build with gradle. I've made further progress on using p2asmaven to make Eclipse update sites available from gradle, so I've good hope I'll manage to get the build working again.