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
[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
- 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
[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
Fixing EffectiveProjectModelFilter caching to cache project model, not the parent model.
Adding unit tests to prevent this from occuring again.
Updating ProjectModelToDatabaseConsumer to adjust model version on unique snapshot after reading from disk, and before the effective project filter.
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@579856 13f79535-47bb-0310-9956-ffa450edef68
- Added and modified code for handling snapshots (if the versions of a specific artifact snapshot are only timestamped versions, add a
generic snapshot which is pointing to the latest timestamp version) in DefaultRepositoryBrowsing and ProjectModelToDatabaseConsumer.
- Updated pom validations in ProjectModelToDatabaseConsumer - handling of timestamped versions were considered
- Added isUniqueSnapshot(..) and isGenericSnapshot(..) in VersionUtil
- Added new attribute 'modelVersion' in DependencyTreeTag to get the in-pom version. Did not use the version attribute so as to retain the
actual version being browsed. Also updated DependencyTree
- Updated the ff. pages for the version to be displayed: artifactInfo.jspf, showArtifact.jsp, dependencyTree.jsp and artifactDecorator.jsp
- Updated the version in SearchResultHit
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@558795 13f79535-47bb-0310-9956-ffa450edef68
* Refactored project resolution into ProjectModelResolverFactory component.
* All resolution access points now use this factory.
* Created ResolverFactoryInit as plexus component load-on-start, to hookup database to resolver stack.
* Created archiva:dependency-tree taglib
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@548008 13f79535-47bb-0310-9956-ffa450edef68
-Added pom validation in ProjectModelToDatabaseConsumer
-Added handling of ObjectNotFoundException in ShowArtifactAction
-Created a new class CorruptArtifactReport for corrupt/invalid pom or artifact repository problem (to be added in database)
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@547209 13f79535-47bb-0310-9956-ffa450edef68
Maria Odea B. Ching
Brett Porter
Joakim Erdfelt
Wendy Smoak