Hi all, I would like to understand why a processed artifact does not have update-db-project consumer in case of a non-unique SNAPSHOT project (please refer to http://jira.codehaus.org/browse/MRM-622 for more information).
The reason for bringing this up is that the database is not being updated accordingly when a non-unique SNAPSHOT project with dependency version changes is deployed once again to Archiva repository. Even though it contains differences compared to the previous one, it's considered processed already and therefore not updated. It looks like a bug in my opinion and I would like to contribute for this fix. Should I change the query constraint for unprocessed artifacts (ArtifactsProcessedConstraint(false)) so it also retrieves the non-unique SNAPSHOT projects or add a new consumer to processed artifacts for database update ? Any tips or pointers would be appreciated. Thanks, Dário -- View this message in context: http://www.nabble.com/Help-on-how-Archiva-consumers-work-tp14272457p14272457.html Sent from the archiva-dev mailing list archive at Nabble.com.
