Eugene, I want to search for classes from time to time.
The situation is usually something where I have some code and the build mechanism is either non-existent or unreadable. Sometimes its some source code I found on a web page somewhere. But there is, in that code, a reference to some other classes and I don't know where they come from or which version it might be. I would like to find the class in question so I know what jar to include when I build (or so I know how to find the source). Sometimes its some code that just puts /path-to-somewhere/lib/*.jar on the classpath and that lib folder has 50 or 100 jars in it. It bothers my sensibilities to include more than I really need in the classpath so I want to know which jars it is. Now, I know that this doesn't always help. If the class in question is named "Info" or some other generic name and there are lots and lots of classes around with that name, it nigh onto impossible to find. It also doesn't help if the jars in that folder I mentioned above are proprietary. But there's a use case for you (or a user story if you prefer). Thanks. -- Lee On Mon, Feb 23, 2009 at 2:57 PM, Eugene Kuleshov <e...@md.pp.ru> wrote: > > > Deron Eriksson wrote: > > > > ...I wanted a web-based application that would let me search for classes > > in the maven repo and get their dependency information. I also wanted to > > have links to source code and javadocs (if available) and to be able to > > view these online. > > > > This is all good, but my question was more along the line what for you > would > want to search for classes? Especially what for would you want to do that > in > the web browser? > > > Deron Eriksson wrote: > > > > Several web-based maven repo search tools exist, but Nexus is the only > > other online tool that I've seen that offers class searching. Nexus > > currently doesn't offer viewable souce code and javadoc links (that I'm > > aware of), and these are things that I find useful when I am trying to > > figure out what a class does. > > > > I am pretty sure it won't take a much time to provide source browser in > Nexus, the chances are that there might be even an enhancement request for > that already, but yet again, it is unclear why such feature would be > useful, > other then it is just a cool feature. > > > Deron Eriksson wrote: > > > > Since you mentioned it, I would love to see source code and javadocs via > > m2eclipse, although I don't know how other people feel. I would > especially > > like it if I could preview source code/javadocs for a class with > m2eclipse > > before deciding to download a jar and use it in my project. > > > > You already can see the sources in m2eclipse using "Navigate / Open Type > from Maven..." action. It is a no brainer to add a javadoc browser for the > artifact, especially if someone would take a minute and enter an > enhancement > request for that in the project issue tracker > http://jira.codehaus.org/browse/MNGECLIPSE > > > Deron Eriksson wrote: > > > > Every once in a while I have a need to see what's in an archive file. If > > there are javadocs, source code, or images in a jar file, I'd prefer to > > scroll through such content online if I happen to be in a web browser. > > Although Jarvana does this, class and artifact searching is far more > > useful to most people than this feature. Jarvana is first and foremost a > > search engine. > > > > You really need to set your goals straight. Building just a search engine > that doesn't serve a common user's workflow doesn't really make much sense. > > > Deron Eriksson wrote: > > > > ...It seemed that no one had done a really in-depth indexing of the maven > > repo, so we wrote Jarvana. > > > > Have you looked at the Nexus Indexer and the index published for the > central > Maven repository? It is a standalone and extensible component, so don't mix > it up with the Nexus repository manager. At very minimum, instead of > creating gigabyte-sized index you can download a few megabytes of prepared > index. > > > Deron Eriksson wrote: > > > > ...The Jarvana indexes are huge, but no one besides the Jarvana web app > > interacts with these indexes, so criticism of the large indexes really > > doesn't make much sense to me. They are large so we can provide new, > > intrinsically different search capabilities. We will probably add new > > interesting types of searches in the future if we find the time and > > motivation to do so. > > > > I was simply stating the fact that Nexus index, which is a magnitude > smaller > provides pretty much the same information as your web application. > > regards, > Eugene > > > -- > View this message in context: > http://www.nabble.com/New-Maven-Respository-Search-Application-tp21973961p22169956.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com
