archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eshan Sudharaka <esudhar...@gmail.com>
Subject Re: procedure for the stage repo merge implementation
Date Tue, 25 May 2010 06:46:05 GMT
On Tue, May 25, 2010 at 11:59 AM, Deng Ching <oching@apache.org> wrote:

> On Tue, May 25, 2010 at 12:12 PM, Eshan Sudharaka <esudharaka@gmail.com
> >wrote:
>
> >  > >
> > > >
> > > Just to be clear again, you don't need to write/create the
> > > MavenMetaDataCreator, Sh1Creator and MD5Creator classes since we
> already
> > > have them in Archiva. Take a look at the UploadAction in archiva-webapp
> > and
> > > see how the metadata and checksums are generated. It might be
> worthwhile
> > to
> > > move out the code for this from the action class so you can re-use it
> in
> > > the
> > > merging.
> > >
> >
> > >>>> so can we use one class to  to get ther services  from available
> > classes in archiva..?
> >
>
> Yes :)
>
>
> >
> > >
> > > I'm confused about the TargetArtifactDetails, what is the difference
> > > between
> > > the sourceArtifactDetailsList, availableArtifactList and
> > > notAvailableArtifactList?
> >
> >    >>>> if the artifact version that we are going to merge is already
in
> > the  target repository i am going to put it in to availableArtifactList
> > since we need to perforn two diffferent actions for both(target repo hit
> > and
> > target repo not hit)
> >
> >
> So is it correct to assume that the TargetArtifactDetails class will
> contain
> info about the target repository and not a specific target artifact?
>


> >>>>> ya. it is contains info about target repository.We can produce
> available artifacts list in the sorce repo and check those are availble in
> target repo using TargetRepoDetails class(as u have mentioned better to
> rename the TargetArtifactDetails in to TargetRepoDetails). once we have
> compared then we can create the directiry structure.
>
> >
> > > The name of the class itself is also a bit
> > > confusing.. It seems that it contains information about the target
> > > repository, so maybe it should be renamed TargetRepositoryDetails?
> >
>
>
> Thanks,
> Deng
>



-- 
P.A.Eshan Sudharaka
Dept of Computer Science and Engineering
University of Moratuwa
Sri Lanka

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