archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deng Ching <och...@apache.org>
Subject Re: class design for copying artifacts to the target repository
Date Tue, 22 Jun 2010 08:03:36 GMT
On Tue, Jun 22, 2010 at 8:00 AM, Eshan Sudharaka <esudharaka@gmail.com>wrote:

> * get the Artifacts meta data of the source repository using
> SourceArtifacts
> class.
>
> * check weather those artifacts are available in the target repository
> using
> metadata resolver.
>
> so we need to consider following scenarios.
>
>  1). Source artifact does not exist in the target repository.
>  2). Source artifact already exist in the target repository
>
>
> case : 1
>
>    * create folder structure.
>           > check rootname space folder exists. If not create it.
>           > check gruop id folder space exists. if not create it.
>           > check artifact id folder exist. if not create it.
>           > then create a folder name version number.
>    * copy jar or war + pom files.
>    * create check sum files and maven metadata xml file using archiva
> availble classes.
>
> case : 2
>
>    * here we need to allow either replacing existing artifact or skip the
> merging
>    * if we are going to merge follow the same procedure as case 1.
>

Yep, looks good..

-Deng

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message