Upgrade from Tycho 2.6.0 to 2.7.4 => Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:2.7.4:validate-classpath #2457
-
Since I upgraded to 2.7.4 some jobs fails with the following pattern:
I have different jobs failing on different plugins in a similar way (just on different plugins). As far as I can see the only difference between this jobs which fail and the verify build which always succeed is that the ones falling are nightly builds and that the use different parameters that affect Interestingly the goal Thanks
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Have you tried using dedicated maven repositories fro the jobs? The local m2 repository is not really meant to be shared across jobs, also please note: |
Beta Was this translation helpful? Give feedback.
-
I am running the jobs with |
Beta Was this translation helpful? Give feedback.
-
I work with @rubenporras and I have continued investigating the problem. I found that the problem only occurs when the builds are run on Windows machines. I also found this stack trace for the problem:
(I have removed the part where the exception bubbles up and the Maven stack trace entries) I suspect the problem might be that Windows Defender locks the p2-artifacts.properties file exclusively (especially because it is created as a new temp file and renamed when saving (afaics)). I have asked for the directories used by the builds to be excluded from scanning, but it hasn't been implemented yet. I'll update this discussion once I have a result, but in the meantime I though I'd document what I found so far in case anybody else has similar problems. |
Beta Was this translation helpful? Give feedback.
-
We have done several tests disabling Windows Defender or the Windows Indexer, but that did not help. However, by upgrading our Windows from to Windows Server 2022, the problem is solved. Thanks for your help. |
Beta Was this translation helpful? Give feedback.
We have done several tests disabling Windows Defender or the Windows Indexer, but that did not help.
However, by upgrading our Windows from to Windows Server 2022, the problem is solved.
Thanks for your help.