On Tue, May 25, 2010 at 12:12 PM, Eshan Sudharaka <[email protected]>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? > > > 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
