I don't really see when I would use the this. When I have JAR with unknown contents and I want to see version and dependencies of it?
At a guess, may be useful when: * Working with old enterprise libraries ("just use the jar!") * Optimisation when dealing with a compile to JVM language like Closure or Scala * Research, such as reverse engineering badly behaved jars.
Show HN: Graffiti – jar analyser
21–25 of 25 posts
Re: Show HN: Graffiti – jar analyser
#22Earlier quoted context omitted.
You can click on the demo link http://graffiti.gaurs.io/downloadDemo ; This points to already processed commons-lang3-3.5.jar
You should host the unzip html pages of the example on your : no effort for user to see what it's look like
Re: Show HN: Graffiti – jar analyser
#23> org.apache.commons.lang3.AnnotationUtils
> The class is part of java.lang.Object package [...]
Interesting package name :)
Re: Show HN: Graffiti – jar analyser
#24From the downloadable example: > org.apache.commons.lang3.AnnotationUtils > The class is part of java.lang.Object package [...] Interesting package name :)
Re: Show HN: Graffiti – jar analyser
#25Some time ago I've started a maven-storyteller-plugin (a version can be found here: https://github.com/highsource/storyteller-maven-plugin ). This plugin was intended to solve a simple task: given a Maven project, which dependencies do you really need and which not? What can (or should) you remove or exclude? maven-storyteller-pluging analyzed the dependency structure of the project (JARs), dependencies of classes, b…