-applied the part for removing the project model from the effective cache of the archiva-database-consumers.patch submitted by
Dario Oliveros
-delete the project model from the db if it already exists in ProjectModelToDatabaseConsumer
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@637928 13f79535-47bb-0310-9956-ffa450edef68
Applied patch submitted by Dario Oliveros
-added RepositoryProblemByArtifactConstraint for querying repo problems by artifact
-remove repo problems if artifact no longer exists in the repo
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@628473 13f79535-47bb-0310-9956-ffa450edef68
- fixed up DaysOldRepositoryPurge
- added test case for the fix
- updated existing test cases
- replaced actual jar and pom files used in the test cases with dummies
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@614840 13f79535-47bb-0310-9956-ffa450edef68
- modified logic for deleting released snapshots, delete only if there exists a released version of that snapshot not when there is a
higher released/snapshot version
- adjusted tests
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@592657 13f79535-47bb-0310-9956-ffa450edef68
- respect set retention count when purging by number of days old (used same logic for purging by retention count)
- updated edit managed repository validation for the number of days old minimum range
- adjusted DaysOldRepositoryPurgeTest for the changes
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@592297 13f79535-47bb-0310-9956-ffa450edef68
[MRM-549] proxy connectors: no "always" option for releases and snapshots policies
Applying changes to policy naming per decisions made in dev@archiva mailing list.
Updating DefaultArchivaConfiguration.load() to automatically adjust old configuration settings to new values.
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@590908 13f79535-47bb-0310-9956-ffa450edef68
-synchronized the index operations in LuceneRepositoryContentIndex (used 'repository' as the lock) to avoid index locking
-added method for deleting artifacts from the index during repository purge
-updated repository purge tests
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@588598 13f79535-47bb-0310-9956-ffa450edef68
- added method for deleting the artifacts in the db when a repo is deleted
- also deleted repo scan statistics when the repo is deleted
- created DAO that does retrieving, deleting and adding of RepositoryContentStatistics to the db
- added and updated tests
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@586919 13f79535-47bb-0310-9956-ffa450edef68
- added code for cleaning up the database of artifacts that are no longer existing in the repository
(DatabaseCleanupRemoveArtifactConsumer and DatabaseCleanupRemoveProjectConsumer)
- created tests for database cleanup of removed artifacts
- updated some of the test cases (in archiva-database and archiva-scheduled modules) to reflect the changes in thedb cleanup consumers
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@584735 13f79535-47bb-0310-9956-ffa450edef68
Replacing with more reliable ManagedRepositoryContent operations.
Cleaning up logging output.
Using new ManagedRepositoryContent.toFile( ArchivaArtifact ) method.
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@584216 13f79535-47bb-0310-9956-ffa450edef68
Corrected the assumption that a Managed Repository is the same as a Local Repository. (re: maven-metadata-local.xml)
Streamlined asserts to be more clear .assertExists() .assertDeleted() when reading code and when error message is created.
Removed jdom direct usage in unit tests in favor of XMLUnit.
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@584213 13f79535-47bb-0310-9956-ffa450edef68
[MRM-519] fail to resolve artifactId for libs that contain versionKeyword in artifactId, like "maven-test-plugin"
[MRM-518] Changing the internal repository directory has no effect
[MRM-512] Unable to convert null repository config to archiva repository.
[MRM-533] metadata-updater is changing lastUpdating timestamp when it shouldn't
[MRM-493] Downloaded artifacts are stored in incorrect archiva-managed repository
- Work against proposal in mailing list http://www.nabble.com/-Proposal--Repository-Layout-Detection-Interaction-Changes.-tf4577852.html
- Creation of package org.apache.maven.archiva.repository.content
- Creation of RepositoryContent alternative as outlined in proposal.
- Have not swung all code over to new repositorycontent object yet.
- Left old BidirectionalRepositoryLayout classes in place temporarily.
- Migrated the following over to new RepositoryContent objects...
* the /repository/ url
* proxying
* metadata updating
* repository purge classes
- Unit testing. Lots and lots of unit testing.
- Correcting bad template email address.
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@583412 13f79535-47bb-0310-9956-ffa450edef68
ArchivaRepository has been removed from model.
This work was needed before repository layout/detection proposal work is started.
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@582987 13f79535-47bb-0310-9956-ffa450edef68
Maria Odea B. Ching
Joakim Erdfelt
Brett Porter