Hi,
If i read this subject of this email then i rather have a way better fix right into Tycho.
I use a "target" site in my pom/tycho configuration
This is not local but the real thing
Why is it if it is already builded with that on jenkins for many times already it can fail suddenly if one of the sites has a hiccup?
Why does it want to continuously check and download the stuff?
Why can't tycho not make a local site right from my target ?
For example generate a sha hash from the contents of the target file
and cache based on that hash on local disk the full resolved site.
(or it fills up in that dir the stuff it needs or it encounters that is not there)
So when a full build is done everything is in that dir based on the sha hash of the contents of that target file
if that file changes it just generates a new one (i guess we need to be able to clean up stuff later )
But as long as the sha hash doesn't change tycho doesn't try to contact any site it always gets everything locally
This should speed up the builds, and we shouldn't suddenly have breaking builds because of a network problem to one of the things inside the target.
This is kind of currently how we work with target files in our Eclipse environments
But then more manually (a user checks the hash ;) )
We have our main target file with the urls, and everybody just exports that to a local site and use that local.target as the real target in eclipse
Because eclipse has the same problems, if there is somehow suddenly an io exception it could even be that you can't really work anymore because the target is just bombing out...
Maybe tycho only needs to cache the contents.jar/artifacts.jar of the sites? because the plugins/features are already cached in the mvn repo. So what we cache based on a sha hash is very little.
Johan