Re: libquartz-java v2 has incomptabilities with previous version
Hello,
Mathieu Malaterre wrote:
[CC me please]
Dead Java-gurus,
Could someone please let me know how can I check whether or not a
java jar is compatible with a past version ?
1. Download Java ACC tool:
https://github.com/lvc/japi-compliance-checker/downloads/
2. Install: sudo perl Makefile.pl -install --prefix=/usr
3. Run: japi-compliance-checker -old OLD.jar -new NEW.jar
See http://ispras.linuxbase.org/index.php/Java_API_Compliance_Checker
for more info.
Another way is to ask to add the library to the
http://upstream-tracker.org/java/
Apparently libquartz-java 2.x is not compatible with 1.x version. Am
I reading the following correctly:
http://mvnrepository.com/artifact/org.quartz-scheduler/quartz
Shouldn't all version ve compatible ?
See http://upstream-tracker.org/java/versions/quartz.html
Thanks !
On Mon, Apr 16, 2012 at 6:23 PM, olivier.sallou@codeless.fr
<olivier.sallou@codeless.fr> wrote:
Hi Mathieu,
I am forwarding this email to you directly as you are the one who uploaded latest release of libquarzt-java.
I sent the mail first to pkg-java-maintainers mailing.
Thanks
Olivier
-------- Message original --------
Sujet: libquartz-java v2 has incomptabilities with previous version
Date : Fri, 13 Apr 2012 15:13:52 +0200
De : Olivier Sallou<olivier.sallou@irisa.fr>
Répondre à : osallou@debian.org
Pour : pkg-java-maintainers@lists.alioth.debian.org
Hi,
recent upload of quartz v2.1.4 in sid created some issue in one of my
package and will certainly impact many other packages.
The change from v1.x to 2.x introduced some incompatibilities in APIs.
There is a backward compatibility jar but it does not solve all problems.
This result in failure even in "common" usages.
Shouldn't package be named libquartz2-java to keep compatibility with
packages depending on previous version ? and as such supporting dual
versions ?
Olivier
--
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
--
Mathieu
--
Andrey Ponomarenko, ROSA Lab.
Reply to: