Introduction prior GSOC
by Vipul Amler
Hi all,
I am Vipul A. M. a Final Year Computer Science Student.
I am interested to work on Java API/ABI changes checker proposed by
Stanislav Ochotnický
over here [1].
I have been having discussions with him for the past 1-2 weeks and getting
to know more about the Java Packaging
System needs on Fedora{and other, need of all platforms as he says}, and
the various pathways for [1]
Till now, I have been trying to understand more how and where the need for
[1] is
as also the available solutions, and pathways there could be. Me learning
from Java API Compliance Checker [2] and others
our discussions have come down to,
* Developing a Java based framework for matching results for single jar to
that of [1]
* Work on build environment to analyse the breakage at CLASSPATH and other
relevant levels
* Create a comparison based large database for analyzing or suggesting how
to proceed ahead.
* Generate outputs of comparison{in different forms json,xml,etc} that
could be further parsed for other purposes
* Generate Web-View of the same
Some of the use-cases suggested for these are as below
Quoting Stanislav
"
I envision following use cases:
1. packagers will run this on new release of upstream jar, and old
release of upstream jar, compare results and decide how to proceed
2. generate a big database of comparison data for a lot of different
versions of various projects/jars where developers can go and see
the stuff without actually running the tool themselves
3. [possibly in the far future] runs by automatic quality control
tools such as AutoQA that would prevent an update to a package in a
released version of distribution that would break compatibility.
"
So,
what I would try and target more in {the very small 3 months of} GSoC ,is
to first develop a base solution that does
proper analysis and breakage detection at singular unit of jar/build
environment.
After a good base try and handle as many features suggested above, in
future.
I would like hear your thoughts/criticisms, to help me identify any other
approaches.
Cheers
[1]
https://fedoraproject.org/wiki/Summer_coding_ideas_for_2012#Java_API.2FAB...
[2] http://ispras.linuxbase.org/index.php/Java_API_Compliance_Checker
Vipul A.M.
+91-8149-204995
12 years
Fwd: Proposal: Java API changes checker
by Alexander Mezin
Hello.
I've created a proposal at
https://fedoraproject.org/wiki/GSOC_2012/Student_Application_Alexandermez...
I propose an utility that will be able to automatically generate
information about classes/methods inside the .jars and classes/methods
required by the .jars, and check if all of the dependencies are
satisfied. Additionally, it will be able to list all known
dependencies of some .jar. Checking of API changes that break
something is only one of possible use cases.
I've just read Vipul Amler's proposal on the same project idea:
https://fedoraproject.org/wiki/GSOC_2012/Student_Application_Vipulnsward/...
Main differences from his proposed project:
1. If I'm not mistaken, he focuses on listing API changes only. I
propose a tool that will generate list of dependencies from class
files/jars/packages - useful for package maintainers.
2. I will implement it in Java. I think that it's better to write
tools for Java in Java itself.
12 years