Laurie Harper wrote: > 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 sure it has the ability to download the index and search from a remote repository, yes. > 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. Ok, I thought Kenney said it did - I haven't used it as an IDEA user myself. I'm not sure if the index will help with tree navigation - I haven't checked if Lucene can enumerate all of the keys (which would allow you to get all the group, artifact and versions in the repository) > 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 was referring to if you are building a comprehensive m2 plugin for IDEA. If you are just interested in the repository function, you might also check out the Raven project (they only have m1 format as well, but maybe you could add m2 support there). Just trying to save you some extra work where possible :) I don't think anyone is parsing the m2 layout at the moment though. The key thing to look for should be the artifact files themselves. From there you can walk back - the directory is the version, the one above that is the artifact, and all the ones above that are group parts. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
