Okay, I've played with Tattletale and two things immediately sprang to
mind:

1. They list the dependencies of the particular jar *first*, which
means that you have to scroll past that list of "org.w3c"... to get to
what the jar actually provides.

2. Because the output is just a bunch of static html files, there's no
search functionality; instead of peeking into the jars themselves
looking for what I need, I can go through the html page for each jar
file instead. Yes this is nicer, but, in my opinion, just a slightly-
better version of the same insanity from before.

Regarding #2 above, I understand it's just  bunch of html files, this
is v1.0, etc., and if I really wanted to, I could just grep the
package name from the html files.

I am not in any way putting down the folks who wrote Tattletale (I'd
love them to reverse the dependencies/provides section), but it seems
like this is a solution that only gets us a half step further from
where we are now. Reading through some of the other responses, it's
actually something of a relief to know that everyone is, to some
extent, struggling with the same issue.


On May 7, 10:01 am, [email protected] (Dominic Mitchell) wrote:
> On Wed, May 06, 2009 at 08:03:01PM -0700, Dick Wall wrote:
>
> > We have a story in the upcoming podcast about JBoss Tattletale -
> >http://www.jboss.org/tattletale- sounds like it might help, and it's
> > from JBoss as well :-).
>
> Oooh, thanks for mentioning that.  I've just tried it and it's dead
> handy -- it found loads of duplicated bits of apache commons that I need
> to sort out.
>
> And it even looks like they're working on making a maven plugin for it
> too.
>
> -Dom
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to