-
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
Build with a nested target platform fails to "bootstrap" #665
Comments
I have attached a full log of the build (note that it is quite long because Maven was also downloading Tycho): out.log. The issue is relevant because a "pristine" Maven environment is not that uncommon in CI environments, so this problem could cause builds to succeed in the developer's machine and then fail on CI. |
I'm not sure, do you mean it fails with an empty maven local repository and succeeds on second build? |
@habbit-baggins I could reproduce this with an empty mvn local repository now. The problem is that we don't add the artifact repository of the referenced target to the overall target content, I'm currently preparing a fix. |
…downloaded Signed-off-by: Christoph Läubrich <laeubi@laeubi-soft.de>
Signed-off-by: Christoph Läubrich <laeubi@laeubi-soft.de>
Cherry picked to 2.7.0 as well. |
I confirm that it works in a pristine Maven environment both in Linux and in Windows, thanks a lot! |
Thanks for verification. If you like this feature the consider say thank you or even sponsor further development of tycho. |
Trying to build the nested target platform example project in a "pristine" environment fails with an exception when trying to validate the classpath of the
test.bundle
project.If the project has ever been built without the nested target platforms (e.g. by using
base.target
as the actual TP in the project), then the problem does not appear, even when using the nested TP.Environment
I was originally testing this in the context of the 2.7 release (#651) but the same problem happens also in master and in the current release 2.6.0 (although earlier in the build).
Steps to reproduce
$ podman run --rm -it -v "$X/tycho-its/projects/target.references:/mnt" maven:3.8-jdk-11 mvn -f /mnt clean verify
The build fails with the mentioned exception, while it should succeed instead.
The text was updated successfully, but these errors were encountered: