Filling out the --extraclasspath argument or moving class/jar files to a specific directory is tedious.
Feature description
Put simply, it would be very convenient if CFR could read the classpath of a jar directly from the manifest, so we would not have to do what I said above. Adding an argument like --detectclasspath with that feature would be nice. It should probably only detect the classpath from the file what is being decompiled, unless doing it for every jar in the classpath is easy, which I doubt.
Problem solved by this feature
Filling out the
--extraclasspathargument or moving class/jar files to a specific directory is tedious.Feature description
Put simply, it would be very convenient if CFR could read the classpath of a jar directly from the manifest, so we would not have to do what I said above. Adding an argument like
--detectclasspathwith that feature would be nice. It should probably only detect the classpath from the file what is being decompiled, unless doing it for every jar in the classpath is easy, which I doubt.Considerations
Alternatives