On 1/17/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Hi Jerome,
It sounds interesting, although how would it be used? Obviously Maven
normally generates the class files, so decompiling target/classes
would be a bit pointless. I guess you could point the plugin at a jar
and it could create a Maven project with sources perhaps?
It's true that most of the time I need to decompile stuff that is not
generated from my source, althought today I needed to decompile a
class to which a third party plugin had added bytecode at build time.
So I wanted to know what this added code was doing...
mvn jad:project
Another use case would be to ask to decompile one or all the
dependencies of a project.
mvn jad:dep -Ddep=commons-io:commons-io [-Dclass=the.Class]
Useful when you don't have access to the source and need to fix a bug...
Raphael's use case might be interesting but maybe harder. One would
need a query service to identify a jar based on the class used (ala
jarhoo.com). Then you have the problem of identifying the right
version of the package. Etc..
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
