Use commons-beanutils-core 1.8.3-SONATYPE
fix comment
Omit 'Latest:' version only when search actually had too many results
Merge pull request #700 from sonatype/NEXUS-5336-update-commons-beanutils

Use commons-beanutils-core 1.8.3-SONATYPE
NXCM-4546 remove example jetty file not intended to be shipped
Making IT more robust.
IT 570: Undoing addition of packaging,

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
[NEXUS-5448] info -> debug
Fix MUtils to handle 'too short' checksums

Unguarded index of " " was triggering an exception and resulted in
relaying HTTP 500 status for staging close with checksum rule check.
Nexus570IndexArchetypeIT fix, take two.

Last failure:
https://bamboo.zion.sonatype.com/browse/NXO-OSST-118

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.
removed pointless test

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
NEXUS-5447 treat duplicate repository add as an error

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 <igor@ifedorenko.com>
Better handling of concurrent index delete operation

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 <igor@ifedorenko.com>
fixing copyright headers

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
NEXUS-5447 clarified "cannot delete index" condition detection

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
NEXUS-5447 clear interrupted flag in InterruptableInputStream

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 <igor@ifedorenko.com>
NEXUS-5447 fixed log message parameter count

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
Merge pull request #702 from sonatype/NEXUS-5447_concurrent_index_remove

Nexus 5447 concurrent index remove
UT fix.

The UT had side effects that made UT fail
when execution order change.

Simply put, 1st method expected to be run
before 2nd method, and it was not clearing
"extra headers" from error servlet, while
2nd method did add extra headers.

Last failure:
https://bamboo.zion.sonatype.com/browse/NXO-OSSJ7-BLD-38
[NEXUS-5455] Menu items were initialized before stores were loaded