Some function parameters named arg0, arg1, etc. After compiling the JAR library

Question

It seems that I ran into a problem in which, after Ant compiling the Jar library, some function parameters are arg0, arg1, etc. instead of their real names. all problematic functions belong to one internal interface in the library.

I compile the library using the Ant command:

ant clean release -Dversion.code = 1 -Dverbose = true -Ddebug = true -Ddebuglevel = "vars"

Given this, for some reason, some methods lose their parameter names, while others retain their parameter names. i.e:.

Func a (String specificName1) turns into (String arg0)

a

Func b (String specificcName2) turns into b (String specificName2)

The question is: There is an internal interface inside the library. Why do interface functions get parameters named arg0, arg1, etc., whereas other methods retain their correct parameter names?

---

I am working on an Android library and I am testing the jar library on the Eclipse IDE.

The compilation itself has been edited in Androids own Ant build.xml:

<javac encoding="${java.encoding}" source="${java.source}" target="${java.target}" debug="true" debuglevel="vars" extdirs="" includeantruntime="false" destdir="${out.classes.absolute.dir}" bootclasspathref="project.target.class.path" verbose="${verbose}" classpathref="project.javac.classpath" fork="${need.javac.fork}"> <src path="${source.absolute.dir}" /> <src path="${gen.absolute.dir}" /> <compilerarg line="${java.compilerargs}" /> </javac> 

Answer 1

Ok, finally found the answers, hope this helps someone:

Story: Parameter names can be taken from javadoc, external source files, or inside the classes themselves. the new thing is that when trying to get information about the parameter name from the class itself, the interface classes cannot save their parameter names like regular classes (according to the Oracle Java specification manual).

This was actually answered in other posts that I hadn't found before:

Java method parameter names from a JAR file in Eclipse

this also does not support the solution to this problem:

Saving parameter / argument names in compiled java classes