There is a very good example on expanding tree in the book "Swing Second Edition", source code free available. http://www.manning.com/books/robinson2/source look in chapter, 17, 23 and 24. These trees grows as they discover new content. If you then use one of the html-parser here http://java-source.net/open-source/html-parsers to parse the m2 repo then you have a good start. _____
From: Laurie Harper [mailto:[EMAIL PROTECTED] To: [email protected] Sent: Sun, 26 Mar 2006 08:14:56 +0200 Subject: Re: Repository navigation Brett Porter wrote: > It uses (will use) the same code as that in the repository manager. > Basically, the repository has a zip of the index that is downloaded > regularly and used to search, making it possible to search remotely. As far as I could tell, m2eclipse uses the same Indexer code, but runs it against the local repo only. Are you saying that maven repositories will, at some point in the future, contain an index as generated by that code? > I'm not sure that helps with browsing - I haven't investigated how the > tree is done there. m2eclipse doesn't have a tree, just a search query/results view. I haven't looked at the index format so I don't know if it would support tree-like navigation. > Have you consulted with the mevenide project? They have developed a > netbeans plugin and have an IDEA plugin for maven 1.x, with the same > developer interested in looking at m2 when time permits. I've tried, but unsuccessfully; for some reason Gmane can't post to the mevenide lists, so I'll have to subscribe by email and try again :-) I've looked at their m1 code for IDEA, but as I mentioned before, this is much easier with an m1 repo layout since you know a priori. I have a hacked-up implementation that works for m2 repo layouts now, by always reading two levels deeper into the tree to figure out if the current directory represents a (part of a) group ID or an artifact ID, but I'm expecting what I have to break down if the current directory represents both... And what I have wont work against a legacy repo layout :-( L. > > - Brett > > Laurie Harper wrote: >> Which one? I've looked at the M2 Eclipse plugin (m2eclipse, from >> Mergere), but that only seems to provide an index search of the local >> repository, no remote repo support. >> >> L. >> >> Kenney Westerhof wrote: >>> On Fri, 24 Mar 2006, Laurie Harper wrote: >>> >>> The Maven plugin for Eclipse presents a tree-view of all dependencies >>> there, maybe you can use some of that code, although I think it's hard to >>> come by. >>> >>> -- Kenney >>> >>>> Ah, OK, so that only works with local repositories, and will scan the >>>> entire repo in one go. I need to be able to work against remote >>>> repositories and perform incremental discovery (think tree view, loading >>>> only as much as necessary to display each sub-tree on node expansion). >>>> >>>> I think there's code here I can steal though :-) And if I can figure out >>>> how to meet my requirements in a way that fits, I'll try to offer some >>>> extensions of the existing m-r-d stuff. >>>> >>>> L. >>>> >>>> Laurie Harper wrote: >>>>> Brett Porter wrote: >>>>>> Take a look at the repository-manager code in SVN, specifically >>>>>> maven-repository-discovery. >>>>> That sounds promising, I hadn't come across that. How come it's in >>>>> /maven, not /maven/components? Maybe that'll become clear once I finish >>>>> checking it out and have a look at the code... >>>>> >>>>>> What type of browser are you trying to build - a web client? >>>>> Nope, an IDE plugin (Maven2 support for IDEA) :-) >>>>> >>>>> L. >>>>> >>>>>> - Brett >>>>>> >>>>>> Laurie Harper wrote: >>>>>>> Does M2 have any APIs for repository navigation and artifact >>>>>>> discovery? >>>>>>> I'm trying to create a repository browser which presents a tree view, >>>>>>> which is easy with M1's 'flat' layout, but with M2's hierarchical >>>>>>> layout >>>>>>> it's a bit trickier... >>>>>>> >>>>>>> Specifically, I don't immediately see a way of figuring out whether a >>>>>>> directory represents (part of) a group ID or an artifact ID until >>>>>>> I look >>>>>>> at its child entries, possibly grand-child entries too. >>>>>>> >>>>>>> It occurs to me that Maven may already abstract all the logic for >>>>>>> doing >>>>>>> this transparently across both repository layout formats... Am I in >>>>>>> luck? :-) >>>>>>> >>>>>>> L. >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>> -- >>> Kenney Westerhof >>> http://www.neonics.com >>> GPG public key: http://www.gods.nl/~forge/kenneyw.key >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
