Permalink
Commits on Apr 1, 2013
  1. nexus oss 2.4.0-07

    Signed-off-by: Sonatype Release Machine <release@sonatype.com>
    Sonatype Release Machine committed Apr 1, 2013
  2. forge parent 34

    Sonatype Release Machine committed Apr 1, 2013
  3. Cleanup: renamed and documented purpose of ConstrainedExecutor

    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Apr 1, 2013
  4. NEXUS-5654 fixed race between offer/revoke and initializePrefixFile

    The race was only possible if a new repository was provisioned and
    deploys to the new repository happened very close in time. Extremely
    unlikely unless repository provisioning and deployment are executed
    by the same script.
    
    The fix is to remove redundant 'unpublish' call during
    initializePrefixFile.
    
    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Apr 1, 2013
  5. NEXUS-5654 fixed endless autorouting initialization restart

    Hosted repositories autorouting initialization involves deep walk
    of entire repository local storage and is likely to take significant
    time for large nexus installations like OSSRH. In attempt to prevent
    lost-update race between artifact deploy/delete and hosted repositry
    autorouting initiazation, deploy/delete unconditionally restarted
    initization which could lead to apparently endless initialization if
    time between deployment is less than initiazation time (again, not
    impossible for larger nexus installations).
    
    The fix is to never restart initialization logic during artifact
    deploy. This is not bulletproof and can result in missing prefix
    entries if deployment of new top-level groupId happens after certain
    point during repository autorouting initiazation, but I believe
    this is going to be very unlikely (assumption is that new top
    groupIds are very rare for populated hosted repositories and
    initiazation is very quick for new/empty hosted repositories). If
    this does happen, the workaround is to delete prefix file and
    wait for 1hr for another initilization attempt to take place.
    
    In order to completely eliminate possibility of race between
    artifact deploy and autorouting initiazation we'd need to extend
    RepositoryItemUidLock API to allow lock-with-timeout, something
    I decided was too tricky and risky this late in 2.4 cycle.
    
    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Apr 1, 2013
  6. Cleanup: removed unused method parameter

    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Apr 1, 2013
  7. Cleanup: reconciled autorouting startup and periodic update logic

    Automatic routing periodic update logic is now able to initialize
    hosted repository prefix path list as needed. No need to do this
    explicitly during startup any more.
    
    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Mar 30, 2013
  8. Fixed wrong RoutingStatusResourceTest initialization sequence

    The test was waiting for routing background updates to finish
    way too early (before nexus repo manager was started) and was
    extremely sensitive to changes auto-routing implementation.
    
    Changed the test to do waiting later during nexus instance
    startup. This is still a workaround and the true fix should
    wait for a particular event, "repo auto-routing publish state
    change" in this case, not for "no backgroup update jobs are
    running" as it does now.
    
    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Mar 31, 2013
  9. Cleanup: removed separate no-scrape marker file

    Changed prefix file format to allow encoding of no-scrape request
    using "@ unsupported" directive. Single automatic routing medata
    file makes proper synchronization easier to implement and simplifies
    overall implementation.
    
    This also eliminated two HEAD requests per remote (due to a bug
    original implementation performed HEAD no-scrape file for each
    discovery strategy, not once per remote).
    
    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Mar 30, 2013
Commits on Mar 30, 2013
  1. Cleanup: removed extra prefix and noscrape paths

    There is currently no use case for these extra file paths,
    they complicate the code and make proper synchronization
    harder to implement.
    
    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Mar 30, 2013
  2. NEXUS-5654 fixed deadlock during concurrent deploy

    Propagation of prefix file changes from members to group repositories
    was acquiring read-lock on all group members while holding write-lock
    on one of the members. Two such changes executed concurrently for
    different members of the same group will almost certainly result in
    deadlock. Solution is to execution group prefix file update on a
    separate thread.
    
    Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
    ifedorenko committed Mar 30, 2013
Commits on Mar 29, 2013
  1. Fixing the build.

    Prefix updates happens async on config
    save, and the UT did not properly wait for
    them.
    cstamas committed Mar 29, 2013
  2. Merge pull request #792 from sonatype/nexus-5602-using-updater-for-in…

    …itial-update
    
    REVIEW: NEXUS-5602: Using the periodic update thread for initial updates too
    cstamas committed Mar 29, 2013
Commits on Mar 28, 2013
  1. NEXUS-5602: Using the periodic update thread for initial updates too

    On 1st boot of updated instances, a lot of MavenRepository
    instances (hosted and proxy) will be piled up in the array
    needUpdateRepositories in WLManagerImpl#startup().
    
    Currently, as the thread pool with fixed size of 5 and
    blocking queue was deferring update.
    
    With this change, the for-loop doing initial WL build
    (walk of the content for hosted and discovery for proxies)
    is deferred, and periodic updater thread is used.
    
    This also means, that upon boot, the initial delay of
    first run will be applied, and on that moment on, hosted
    reposes will have WL, not before that.
    
    Initial change breaks all the UTs and ITs that uses
    exposed-for-tests-only method to reach a state when
    the test should start.
    
    isUpdateWhitelistJobRunning() method used for this
    is now updated, and will flag (and make tests wait)
    as long as boot sequence is done (newly added) AND
    there are no bg updates running (as before).
    
    Also, EventDispatcher simplified, the feature active
    flag is not passed anymore, instead, it is not
    registered to event bus when feature is not
    active, resulting in same behavior (before, when
    feature was inactive EventDispatcher got events
    but simply did not invoke WL Manager).
    cstamas committed Mar 27, 2013
  2. Back to version 2.4-SNAPSHOT

    ifedorenko committed Mar 28, 2013
  3. Merge pull request #795 from sonatype/nexus-5639-rename-wl-deep

    [blocker 2.4] NEXUS-5639: Deep rename of WL into Routing
    cstamas committed Mar 28, 2013
  4. Merge pull request #794 from sonatype/nexus-5639-rename-wl

    [2.4 blocker] NEXUS-5639: Rename WL
    cstamas committed Mar 28, 2013
  5. NEXUS-5639: Rename thread names

    From "wl" to "ar" as Auto routing...
    cstamas committed Mar 28, 2013
  6. NEXUS-5639: M2 repo external config change

    Renamed externalConfiguration nodes too
    cstamas committed Mar 28, 2013
  7. NEXUS-5639: URL change of the resources

    Client is handled too
    cstamas committed Mar 28, 2013
  8. NEXUS-5639: "Deep" rename WL to Routing

    Initial code changes, bundle smoke tested and is working.
    
    Tests and ITs not verified yet.
    cstamas committed Mar 28, 2013
  9. NEXUS-5639: Cleaning log messages

    In AbstractMavenRepo
    cstamas committed Mar 28, 2013
  10. NEXUS-5639: Cleaning log messages

    In WLManagerImpl
    cstamas committed Mar 28, 2013
  11. NEXUS-5639: Cleaning log messages

    In EventDispatcher
    cstamas committed Mar 28, 2013
  12. NEXUS-5639: Rename WL

    UI panel mods:
    * tab title renamed from "Whitelist" to "Routing"
    * tab name changed from "whitelist" to "routing"
    * "Force remote discovery" button renamed to "Update now"
    cstamas committed Mar 28, 2013
Commits on Mar 26, 2013
  1. nexus oss 2.4.0-06

    Signed-off-by: Sonatype Release Machine <release@sonatype.com>
    Sonatype Release Machine committed Mar 26, 2013
  2. Merge pull request #788 from sonatype/one-stylesheet-per-iconcontainer

    REVIEW: Reduce # of dynamic stylesheets for better IE compat
    ifedorenko committed Mar 26, 2013
  3. [NXCM-5148] Install all icon styles for an iconcontainer instance int…

    …o a single stylesheet (ie{8,9,?} have limitations on the # of these before it looses its shit)
    
    Will need to optimize this further to allow all iconcontainer instances to share a single stylesheet so this can scale better past 31
    Remove custom Ext.util.CSS implementation which was handling ie9 due to ^^^, but once ^^^ its not needed.
    jdillon committed Mar 26, 2013
Commits on Mar 25, 2013
  1. Revert changes for NXCM-5131

    This reverts commits 683c647 and
    d4f21a0.
    nabcos committed Mar 25, 2013
Commits on Mar 22, 2013
  1. Merge pull request #780 from sonatype/nexus-5608-group-wl-double-update

    WL update misbehaving
    cstamas committed Mar 22, 2013
  2. Merge pull request #784 from sonatype/nxcm-5131-nuget-proxy-conf

    [NXCM-5131] Change item age value type from Integer to int
    nabcos committed Mar 22, 2013
  3. Extended WL update tests to GoG

    Group of group checks introduced in the UTs.
    cstamas committed Mar 22, 2013
  4. UT testing WL content on member change.

    There was no UT directly testing for correct WL
    content on group member changes (only "update propagation"
    was tested).
    cstamas committed Mar 22, 2013