Switch branches/tags
pre-merged-nexus-oss pre-merge nexus-test-selenium-pre-testng nexus-test-harness-env-plugin nexus-test-environment-maven-plugin-1.6 nexus-test-environment-maven-plugin-1.5 nexus-test-environment-maven-plugin-1.4 nexus-test-environment-maven-plugin-1.3 nexus-test-environment-maven-plugin-1.2 nexus-test-environment-maven-plugin-1.1 nexus-test-environment-maven-plugin-1.0 nexus-runtime-platform-1 nexus-restlight-clients-1.3.2 nexus-restlight- nexus-repository-metadata-1.1 nexus-repository-metadata-1.1-M1 nexus-repository-metadata-1.0.3 nexus-repository-metadata-1.0.2 nexus-repository-metadata-1.0.1 nexus-repository-metadata-1.0.0 nexus-parent-20 nexus-parent-19 nexus-parent-18 nexus-parent-18-M1 nexus-parent-17.1 nexus-parent-17 nexus-parent-16 nexus-parent-15 nexus-parent-14 nexus-parent-13 nexus-parent-12 nexus-parent-11 nexus-parent-10.1 nexus-parent-10 nexus-parent-9 nexus-parent-8 nexus-parent-7 nexus-parent-6 nexus-parent-5 nexus-parent-4 nexus-parent-3 nexus-parent-2 nexus-parent-1 nexus-migration-tool-1.2 nexus-migration-plugin- nexus-migration-plugin-1.9.2 nexus-migration-plugin-1.9.2-RC3 nexus-migration-plugin-1.9.2-RC2 nexus-migration-plugin-1.9.2-RC1 nexus-migration-plugin-1.9.1 nexus-migration-plugin-1.7 nexus-migration-plugin-1.6 nexus-migration-plugin-1.5 nexus-migration-plugin-1.4 nexus-migration-plugin-1.3 nexus-migration-plugin-1.2 nexus-migration-plugin-1.1.1 nexus-migration-plugin-1.1.0 nexus-migration-plugin-1.0 nexus-maven-plugins-parent-2.1 nexus-maven-plugins-parent-2.1-RC1 nexus-maven-plugin- nexus-maven-plugin-1.9.2 nexus-maven-plugin-1.8 nexus-maven-plugin-1.8-RC3 nexus-maven-plugin-1.8-RC2 nexus-maven-plugin-1.8-RC1 nexus-maven-plugin-1.7 nexus-maven-plugin-1.7-RC1 nexus-maven-plugin-1.6 nexus-maven-plugin-1.5 nexus-maven-plugin-1.4 nexus-maven-plugin-1.3.3 nexus-maven-plugin-1.3.2 nexus-indexer-artifact-1.1-M1 nexus-indexer-artifact-1.0.1 nexus-indexer-artifact-1.0.0 nexus-indexer-3.1-M1 nexus-indexer-3.0.4 nexus-indexer-3.0.3 nexus-indexer-3.0.2 nexus-indexer-3.0.1 nexus-indexer-2.0.6 nexus-indexer-2.0.5 nexus-indexer-2.0.5-central nexus-indexer-2.0.4 nexus-indexer-2.0.3 nexus-indexer-2.0.2 nexus-indexer-2.0.1 nexus-indexer-2.0.0 nexus-indexer-1.2.4 nexus-indexer-1.2.3 nexus-indexer-1.2.2 nexus-indexer-1.2.1 nexus-indexer- nexus-indexer- nexus-indexer- nexus-indexer- nexus-indexer-1.1.2 nexus-indexer-1.1.1
Nothing to show
Commits on Dec 14, 2012
  1. NEXUS-5447 fixed log message parameter count

    ifedorenko committed Dec 14, 2012
    Signed-off-by: Igor Fedorenko <>
  2. NEXUS-5447 clear interrupted flag in InterruptableInputStream

    ifedorenko committed Dec 13, 2012
    The wrapper both aborts underlying http request and throws
    InterruptedIOException. Leaving Thread interrupted flag on may
    trigger unnecessary/unwanted isInterrupted detection in
    unrelated code executed by the thread later on.
    Signed-off-by: Igor Fedorenko <>
  3. NEXUS-5447 clarified "cannot delete index" condition detection

    ifedorenko committed Dec 13, 2012
    Signed-off-by: Igor Fedorenko <>
  4. fixing copyright headers

    ifedorenko committed Dec 13, 2012
    Signed-off-by: Igor Fedorenko <>
  5. Better handling of concurrent index delete operation

    ifedorenko committed Dec 13, 2012
    Similar to index download and other potentionally long runnig
    operations, remove repository index now requires two locks --
    reindex lock and index lock.
    If reindex lock is held by another thread during remove index
    operation, implementation will notify the other thread about
    immenent index removal via Thread #interrupt.
    Regular index access operations like add/remove item and queries
    are skipped if the repository is being deleted.
    Remove index implementation throws IOException if the index was
    not removed for any reason.
    HttpClientRemoteStorage provides best-effect Thread.isInterrupted
    support for remote downloads.
    Signed-off-by: Igor Fedorenko <>
  6. NEXUS-5447 treat duplicate repository add as an error

    ifedorenko committed Dec 12, 2012
    Add repository index requests are not expected for repositories that
    already have existing indexing contexts. Indexing contexts are
    created based on repository registry events, so duplicate events
    almost certainly mean a bug in the registry or elsewhere outside of
    the indexer.
    Do not discard the old indexing context because it may have filesystem
    locks and/or long running threads associated with it. Log the error and
    ignore the duplicate add repository index request.
    Signed-off-by: Igor Fedorenko <>
  7. removed pointless test

    ifedorenko committed Dec 12, 2012
    Signed-off-by: Igor Fedorenko <>
  8. Nexus570IndexArchetypeIT fix, take two.

    cstamas committed Dec 14, 2012
    Last failure:
    This time a small change implemented in AbstractNexusIntegrationTest
    and added proper packaging to the test project being
    deployed as part of preparations for this IT.
    Original assumption still stands, asynchronously run
    event inspector ordering is not guaranteed, and also
    reliability of "wait for ..." IT utilities are questioned
    too (NEXUS-5127).
    With this change (redone), it should never fail again,
    as it will immediately (on POM arrival) be indexed as archetype,
    not JAR anymore.
Commits on Dec 13, 2012
  1. [NEXUS-5448] info -> debug

    jdillon committed Dec 13, 2012
Commits on Dec 12, 2012
  1. IT 570: Undoing addition of packaging,

    cstamas committed Dec 12, 2012
    as it seems old ITs are dumb enough to assume "packaging" ==
    "file extension", they do not "translate". And obviously, in this
    case, "maven-archetype" should have extension JAR
  2. Making IT more robust.

    cstamas committed Dec 12, 2012
Commits on Dec 11, 2012
  1. Merge pull request #700 from sonatype/NEXUS-5336-update-commons-beanu…

    jdillon committed Dec 11, 2012
    Use commons-beanutils-core 1.8.3-SONATYPE
  2. Do not display 'Latest: $version' for collapsed search results

    nabcos committed Dec 11, 2012
    The 'latest' version may be wrong because search is timeboxed and does
    not always gather all available versions.
  3. Display a load mask for UI load

    nabcos committed Dec 11, 2012
  4. Merge pull request #701 from sonatype/nexus-5440

    cstamas committed Dec 11, 2012
    NEXUS-5440: Latest versions incorrectly gathered
  5. Merge pull request #697 from sonatype/nxcm-4852

    cstamas committed Dec 11, 2012
    NXCM-4852: EOF on deploy
  6. NEXUS-5440: UT

    cstamas committed Dec 11, 2012
    UT checks various get methods are doing the "right thing" (tm)
  7. NEXUS-5440: Made the REST resource return ordered versions

    cstamas committed Dec 11, 2012
    REST resource now returns in same "expected" order the versions,
    in descending order, latest being 1st.
    Note: UI _sorts_ the result in grid, but it applies simple
    lexicographical sort, so with this change, UI should
    not default to lexi sort of Versions column.
  8. NEXUS-5440: Latest versions incorrectly gathered

    cstamas committed Dec 11, 2012
    Typo in expression.
  9. [maven-release-plugin] prepare for next development iteration

    Sonatype Release Machine committed Dec 11, 2012
  10. [maven-release-plugin] prepare release nexus-2.3.0

    Sonatype Release Machine committed Dec 11, 2012
  11. depend on forge-parent 30

    peterlynch committed Dec 11, 2012
    we need empty jars in many places in nexus and parent changed the default back to false
  12. NXCM-4546 update jetty example files

    peterlynch committed Dec 11, 2012
    these updates taken from issue attachment as provided by Rich Seddon
  13. fix comment

    jdillon committed Dec 11, 2012
Commits on Dec 10, 2012
  1. NXCM-4852: UT fix

    cstamas committed Dec 10, 2012
    Added check for tmp files too, and changed when EOF is
    thrown to ensure we got _some_ content.
  2. depend on forge-parent 29

    peterlynch committed Dec 10, 2012
  3. NXCM-4852: UT extended

    cstamas committed Dec 10, 2012
    UT is now checking not only the exception being
    thrown when EOF occurs during storing, but also
    that there are no remnant files left in storage.