libquartz-java v2 has incomptabilities with previous version

04-16-2012, 04:35 PM

[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 ?

* 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 ?

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

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CA+7wUszCre5iKnAMNEF0jK_9-jn-qdw4BHZdFjmvSGRZoaKS_g@mail.gmail.com">http://lists.debian.org/CA+7wUszCre5iKnAMNEF0jK_9-jn-qdw4BHZdFjmvSGRZoaKS_g@mail.gmail.com

04-16-2012, 04:47 PM

They released a version 2.0 that is binary incompatible and shares the
same package name and the same Maven artifact, that was a very poor
decision.

Building a libquartz2-java package for Debian is probably a sensible choice.

Emmanuel Bourg

Le 16/04/2012 18:35, Mathieu Malaterre a écrit :

[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 ?

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 ?

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

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4F8C4D0B.1050604@apache.org">http://lists.debian.org/4F8C4D0B.1050604@apache.org

04-17-2012, 07:23 AM

Thanks for the notice. I filled a serious bug against libquartz-java
to prevent migration to testing. I also filled a bug against
ftp.debian.org to remove the package from unstable.

I'll try to fix my mess this week.

Thanks everyone for the quick help.

On Mon, Apr 16, 2012 at 6:47 PM, Emmanuel Bourg <ebourg@apache.org> wrote:
> They released a version 2.0 that is binary incompatible and shares the same
> package name and the same Maven artifact, that was a very poor decision.
>
> Building a libquartz2-java package for Debian is probably a sensible choice.
>
> Emmanuel Bourg
>
>
> Le 16/04/2012 18:35, Mathieu Malaterre a écrit :
>
>> [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 ?
>>
>> * 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 ?
>>
>> 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
>>
>>
>
>
> --
> To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> Archive: http://lists.debian.org/4F8C4D0B.1050604@apache.org
>

--
Mathieu

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CA+7wUsyrp41EiARrS1WgFqpqQeX754dd_j_GdFXHq+f-SMJrNg@mail.gmail.com">http://lists.debian.org/CA+7wUsyrp41EiARrS1WgFqpqQeX754dd_j_GdFXHq+f-SMJrNg@mail.gmail.com

04-17-2012, 07:34 AM

2012/4/16 Mathieu Malaterre <mathieu.malaterre@gmail.com>

[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 ?

* 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 ?

You can find migration info in upstream site only...http://quartz-scheduler.org/documentation/quartz-2.x/migration-guide

But even backward compatibiliy jar file provided with new version does not solve all issues. And it also requires additional jar files in the path (the backward one and slf4j-api too).

Olivier
*
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

--
gpg key id: 4096R/326D8438 (keyring.debian.org)Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438

04-26-2012, 09:05 AM

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.

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4F990FE4.6010105@rosalab.ru">http://lists.debian.org/4F990FE4.6010105@rosalab.ru

04-26-2012, 09:21 AM

Andrey ,

On Thu, Apr 26, 2012 at 11:05 AM, Andrey Ponomarenko
<aponomarenko@rosalab.ru> wrote:
...
> See http://upstream-tracker.org/java/versions/quartz.html

Ok, then. I need a little training here. How can one parse this beasty
table to deduce:

- updating 1.6.6 to 1.7.3 is ok (see past uploads)
- updating 1.7.3 to 2.1.4 is not ok

Thanks much

-M

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: CA+7wUsyc4v9Ro9DHwxp5MbtahKqq3sdG69FmW9rUT+SkH8H4E Q@mail.gmail.com">http://lists.debian.org/CA+7wUsyc4v9Ro9DHwxp5MbtahKqq3sdG69FmW9rUT+SkH8H4E Q@mail.gmail.com

05-05-2012, 11:32 AM

Hi,

Mathieu Malaterre wrote:

Andrey ,

On Thu, Apr 26, 2012 at 11:05 AM, Andrey Ponomarenko
<aponomarenko@rosalab.ru> wrote:
...

See http://upstream-tracker.org/java/versions/quartz.html

Ok, then. I need a little training here. How can one parse this beasty
table to deduce:

- updating 1.6.6 to 1.7.3 is ok (see past uploads)
- updating 1.7.3 to 2.1.4 is not ok

The source compatibility (ability to rebuild dependent clients) of 1.6.6
and 1.7.3 is estimated as 81.3% in the table. But compatibility of 1.7.3
and 2.1.4 is 86.6%*63.5%*79.2%=43.5% that is half as much as for 1.6.6
and 1.7.3.

In any case, if you see any compatibility problems in the table, then
you should try to rebuild and adapt (if needed) all dependent clients
before update, as they may be affected.

All dependent packages can be listed by the command: apt-cache rdepends
libquartz-java

Also, there is a policy for Debian Java libraries [1]. But it doesn't
explain how to update libraries and when to bump a version number in
libXXX[version]-java. Is there other documents for Java package
maintainers in Debian?

[1] Debian policy for Java: 2.3. Java libraries
<http://www.debian.org/doc/packaging-manuals/java-policy/x104.html>

Thanks much

-M

--
Andrey Ponomarenko, ROSA Lab.

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FA50FDE.60405@rosalab.ru">http://lists.debian.org/4FA50FDE.60405@rosalab.ru

05-05-2012, 12:00 PM

Le 5/5/12 1:32 PM, Andrey Ponomarenko a écrit :
> Hi,
>
> Mathieu Malaterre wrote:
>> Andrey ,
>>
>> On Thu, Apr 26, 2012 at 11:05 AM, Andrey Ponomarenko
>> <aponomarenko@rosalab.ru> wrote:
>> ...
>>> See http://upstream-tracker.org/java/versions/quartz.html
>> Ok, then. I need a little training here. How can one parse this beasty
>> table to deduce:
>>
>> - updating 1.6.6 to 1.7.3 is ok (see past uploads)
>> - updating 1.7.3 to 2.1.4 is not ok
>
> The source compatibility (ability to rebuild dependent clients) of
> 1.6.6 and 1.7.3 is estimated as 81.3% in the table. But compatibility
> of 1.7.3 and 2.1.4 is 86.6%*63.5%*79.2%=43.5% that is half as much as
> for 1.6.6 and 1.7.3.
>
> In any case, if you see any compatibility problems in the table, then
> you should try to rebuild and adapt (if needed) all dependent clients
> before update, as they may be affected.
>
> All dependent packages can be listed by the command: apt-cache
> rdepends libquartz-java
>
> Also, there is a policy for Debian Java libraries [1]. But it doesn't
> explain how to update libraries and when to bump a version number in
> libXXX[version]-java. Is there other documents for Java package
> maintainers in Debian?
>
Independently of Java, it is related to Debian libraries management. The
Debian policy on libraries [0], 8.1 paragraph, referring as examples to
SO files, specifies that a different SONAME and binary package name
should be used in case of API breakage.
SO and Java jars have same behavior.

[0] http://www.debian.org/doc/debian-policy/ch-sharedlibs.html

Olivier
> [1] Debian policy for Java: 2.3. Java libraries
> <http://www.debian.org/doc/packaging-manuals/java-policy/x104.html>
>
>>
>> Thanks much
>>
>> -M
>>
>>
>
>
> --
> gpg key id: 4096R/326D8438 (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FA5165B.5070806@codeless.fr">http://lists.debian.org/4FA5165B.5070806@codeless.fr

05-10-2012, 08:52 AM

olivier.sallou@codeless.fr wrote:

Le 5/5/12 1:32 PM, Andrey Ponomarenko a écrit :

Hi,

Mathieu Malaterre wrote:

Andrey ,

On Thu, Apr 26, 2012 at 11:05 AM, Andrey Ponomarenko
<aponomarenko@rosalab.ru> wrote:
...

See http://upstream-tracker.org/java/versions/quartz.html

Ok, then. I need a little training here. How can one parse this beasty
table to deduce:

- updating 1.6.6 to 1.7.3 is ok (see past uploads)
- updating 1.7.3 to 2.1.4 is not ok

The source compatibility (ability to rebuild dependent clients) of
1.6.6 and 1.7.3 is estimated as 81.3% in the table. But compatibility
of 1.7.3 and 2.1.4 is 86.6%*63.5%*79.2%=43.5% that is half as much as
for 1.6.6 and 1.7.3.

In any case, if you see any compatibility problems in the table, then
you should try to rebuild and adapt (if needed) all dependent clients
before update, as they may be affected.

All dependent packages can be listed by the command: apt-cache
rdepends libquartz-java

Also, there is a policy for Debian Java libraries [1]. But it doesn't
explain how to update libraries and when to bump a version number in
libXXX[version]-java. Is there other documents for Java package
maintainers in Debian?

Independently of Java, it is related to Debian libraries management. The
Debian policy on libraries [0], 8.1 paragraph, referring as examples to
SO files, specifies that a different SONAME and binary package name
should be used in case of API breakage.
SO and Java jars have same behavior.

[0] http://www.debian.org/doc/debian-policy/ch-sharedlibs.html

So, according to this policy, the version number in the Java library
package name should be increased whenever the API of the library changes
in a backward-incompatible way.

Olivier

[1] Debian policy for Java: 2.3. Java libraries
<http://www.debian.org/doc/packaging-manuals/java-policy/x104.html>

Thanks much

-M

--
gpg key id: 4096R/326D8438 (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438

--
Andrey Ponomarenko, ROSA Lab.

--
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4FAB81D4.1010601@rosalab.ru">http://lists.debian.org/4FAB81D4.1010601@rosalab.ru