Page History

...

This is the most important part in this project. Once the testing tasks are done this role is responsible for merge artifacts from staging repository to the internal repository or the snapshot repository. It depends on the artifact(snapshot or a version).Here i am going to consider following things regarding the merging the artifacts
If the artifacts that are going to deploy is not an existing one(new one) just deploy it with creating new meta data file. (user should me able to merge the artifact bu clicking the merge button and then should receive to success/failure message from the archiva side)
If the artifact is an existing one(latest version) we need to provide following options.
when the user clicks merge button it should notify the user about the older versions in the release repository.(eg : version numbers + updated date)
then we need to suggest him following options.

• merging the artifact while keeping the older version
• merging the artifact while removing the older version. Here we should only allow to remove latest artifact.
  Eg : in the main repo we have versions 1.1, 1.2, 1.3.And we are going to merge version 1.4.If there are significant changes in version 1.3 and version 1.4 it is better to keep 1.3 version and add 1.4.
  But if there are no significant changes in both artifacts then it is better to remove the version 1.3 and add 1.4.
  Mean while meta data updating also should be done.

In above I have mentioned only the success scenario of a artifact. There can be a fail scenario as well. If an artifact is failed then the user should manually delete the artifact

...