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 <[email protected]> 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, [email protected]
>> <[email protected]>  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<[email protected]>
>>> Répondre à : [email protected]
>>> Pour : [email protected]
>>>
>>>
>>> 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 [email protected]
> with a subject of "unsubscribe". Trouble? Contact
> [email protected]
> Archive: http://lists.debian.org/[email protected]
>



-- 
Mathieu


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: 
http://lists.debian.org/ca+7wusyrp41eiarrs1wgfqpqqex754dd_j_gdfxhq+f-smj...@mail.gmail.com

Reply via email to