On Mon, May 31, 2010 at 9:19 AM, Eshan Sudharaka <[email protected]>wrote:
> <metadata> > <groupId>log4j</groupId> > <artifactId>log4j</artifactId> > <versioning> > <latest>1.2.14</latest> > <release>1.2.14</release> > <versions> > <version>1.2.8</version> > <version>1.2.14</version> > </versions> > </versioning> > </metadata> > by reading this files we can get the list of available artifacts in the > source repo. Then we can do differeent actions for merging for following > cases. > * there is a same artifact in target repo > * no such artifact in target repo > > On Sun, May 30, 2010 at 12:13 PM, Brett Porter <[email protected]> wrote: > >> The image was missing (this list would strip attachments). Maybe you can >> post it to the wiki? >> > > il send the link. > >> >> http://picasaweb.google.com/104163866911029090831/ClassDiagrams#5477276612723378274 >> As for existing tools - the repository scanner is what traverses the >> folder structure, but I'm unsure why you need to do that for the metadata >> files - the mechanism should be artifact centric and the metadata files just >> go along with them. >> >> - Brett >> >> On 28/05/2010, at 7:37 PM, Eshan Sudharaka wrote: >> >> > here i have attached the basic structure of the class. And i want to >> know do i need to implement a search method to iterate through the folder >> structure and find the maven meta data XML files ? or that functionality is >> al;ready there in archiva code base ? >> > >> > -- >> > P.A.Eshan Sudharaka >> > Dept of Computer Science and Engineering >> > University of Moratuwa >> > Sri Lanka >> >> > > > -- > P.A.Eshan Sudharaka > Dept of Computer Science and Engineering > University of Moratuwa > Sri Lanka > -- P.A.Eshan Sudharaka Dept of Computer Science and Engineering University of Moratuwa Sri Lanka
