-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A transient dependency issue is affecting compilation of xtext projects #2077
Comments
I'm seeing the same thing. It's coming from If it helps you, or anyone who stumbles upon this, I was able to get around this for my build by setting a resolutionStrategy like below, though that should just be temporary until this is fixed:
That still brings in |
The workaround above solve the compilation problem but cause another problem in unit tests. I disable my unit tests and froze the changes in language project (xtext project) until the problem is solved.
|
can you please provide a reproducer |
to me this also looks like a bug in eclipse platform and their scripts that create the maven deps |
my gradle builds work,
also https://ci.eclipse.org/xtext/job/releng/job/sign-and-deploy/1580/console |
Signed-off-by: Christian Dietrich <[email protected]>
…platform Signed-off-by: Christian Dietrich <[email protected]>
…platform Signed-off-by: Christian Dietrich <[email protected]>
[eclipse-xtext/xtext#2077] workaround for broken metadata in eclipse platform
…y platform Signed-off-by: Christian Dietrich <[email protected]>
Someone added a dependency on a non-existing artifact in the new Equinox release and now many builds are broken because Xtext defines a version range for Equinox 😞, see: * eclipse-equinox/equinox.bundles#54 * eclipse-xtext/xtext#2077 Signed-off-by: Wouter Born <[email protected]>
Someone added a dependency on a non-existing artifact in the new Equinox release and now many builds are broken because Xtext defines a version range for Equinox 😞, see: * eclipse-equinox/equinox.bundles#54 * eclipse-xtext/xtext#2077 Signed-off-by: Wouter Born <[email protected]>
Apparently the problem has been resolved and I removed exclude directive from my build.gradle.
When investigating the issue, I noticed that there is an override of the equinox version in the build.gradle of my tests.
I removed the equinox override version and the tests passed without error. |
…clipse platform Signed-off-by: Christian Dietrich <[email protected]>
eclipse platform has pulled the bad artifact(s) from maven central. so (at least after the clearing of local maven repos or mirrors) the problem should be solved |
Hi @cdietrich |
Someone added a dependency on a non-existing artifact in the new Equinox release and now many builds are broken because Xtext defines a version range for Equinox 😞, see: * eclipse-equinox/equinox.bundles#54 * eclipse-xtext/xtext#2077 Signed-off-by: Wouter Born <[email protected]> GitOrigin-RevId: af0566a
Hi.
My xtext project stopped compiling today. Apparently a transient dependency has been deleted or modified. See the error below:
The text was updated successfully, but these errors were encountered: