is currently readonly. We are migrating to, please continue working there on Monday 14/12. See:

  • Ard Schrijvers's avatar
    HIPPLUG-1329 [Forward port 3.1] make sure every worker has its own urlset · e80b956a
    Ard Schrijvers authored
    The Urlset object should have to think about synchronization. It is the code
    that uses the Urlset that shouldn't expect the Urlset to be thread-safe (just
    like a HashSet isn't thread-safe. It make much more sense to not give all the
    workers a reference to the same urlset object but all have their own
    A seperate note is that I really think the worker should not extend from
    Thread and a lot of the complex logic can be replaced by a simple executer service
    (cherry picked from commit 031750fa)
Last commit
Last update
src Loading commit data...
pom.xml Loading commit data...