Adding new Metadata Updater Consumer.
Updating archiva-configuration default for new consumer.
Updating archiva-proxy for new Metadata Tools approach.
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@574121 13f79535-47bb-0310-9956-ffa450edef68
- Added tests for metadata driven snapshots in DaysOldRepositoryPurgeTest
- Added test data
Changes made in DaysOldRepositoryPurge:
- Added functionality to consider the metadata driven snapshots (check the timestamp in the filename first before the last modified date of the
file if it is a unique versioned snapshot)
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@570089 13f79535-47bb-0310-9956-ffa450edef68
- Added tests for RepositoryConsumer and CleanupReleasedSnapshotsRepositoryPurge
- Added test data for the new tests
- Refactored AbstractRepositoryPurgeTest, DaysOldRepositoryPurgeTest and RetentionCountRepositoryPurgeTest
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@569789 13f79535-47bb-0310-9956-ffa450edef68
- Changed DefaultCleanupReleasedSnapshots to CleanupReleasedSnapshotsRepositoryPurge
- Removed unneeded fields in RepositoryPurgeConsumer
- Added constructor for DaysOldRepositoryPurge, RetentionCountRepositoryPurge and CleanupReleasedSnapshotsRepositoryPurge
- Updated test classes and test resources
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@563064 13f79535-47bb-0310-9956-ffa450edef68
- Added the test cases which were left out during the initial commit
- Added DefaultCleanupReleasedSnapshots (m2 implementation for cleaning up snapshots that were already released)
- Updated the following files: archiva-core-consumers/pom.xml, RepositoryPurgeConsumer, DaysOldRepositoryPurge, RetentionCountRepositoryPurge and
AbstractRepositoryPurge
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@562882 13f79535-47bb-0310-9956-ffa450edef68
- Added RepositoryPurgeConsumer
- Added these other classes used in repo purge: DaysOldRepositoryPurge, RetentionCountRepositoryPurge, ArtifactFilenameFilter and
RepositoryPurgeException
- Added tests and test data
- Added new fields in configuration.mdo (daysOlder and retentionCount)
- Added repository-purge as a consumer in default-archiva.xml (but currently commented out)
git-svn-id: https://svn.apache.org/repos/asf/maven/archiva/trunk@562766 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
