-
Notifications
You must be signed in to change notification settings - Fork 189
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
NPE on getting execution environment #1745
Comments
What I see is this in the log:
and it seems this one can maybe not be mapped but thats hard to tell from the log snippet, there should be some more output regarding EE found. To further debug this, you might want to compare if there are local "toolchains.xml" and what are on the build server. |
How can I try out a snapshot?
Configuring this, I get:
Also, going to https://repo.eclipse.org/content/repositories/tycho-snapshots in a browser, I get a HTTP 503 error. This is the URL given at both https://github.com/eclipse-tycho/tycho/blob/master/CONTRIBUTING.md and https://wiki.eclipse.org/Getting_Tycho. |
It seems |
Yes the repo is sadly down, whe hope its getting fixed somewhere today. |
Is there already an integration test-case for this bug? I encountered it as well since Tycho 3.0 and can confirm that it is fixed with the latest Tycho 4.0-SNAPSHOT.
I can provide an integration test so that we can ensure the issues does not happen again and Tycho works well with JustJ. In general I wonder if we can't simply the use of JustJ and somehow detect automatically that the JustJ JRE should be used? |
I'm not aware of that
That would be useful indeed.
See
See |
I'm trying to migrate Eclipse ESCET from Tycho 2.7.1 to 3.0.0. Locally, the build succeeds. On Jenkins, it fails, with the following error:
I don't know what happens internally in Tycho, but an NPE sounds like a bug.
The text was updated successfully, but these errors were encountered: