[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#787953: depends on obsolete libasm2-java library



Hi Felix,

Am 09.10.2015 um 23:19 schrieb Felix Natter:
> Markus Koschany <apo@gambaru.de> writes:
[...]
> 
> Please also tell him/her that I have patches for converting jajuk to
> insubstantial 7.3:
>   https://github.com/fnatter/insubstantial-debian/blob/rdeps/rdeps/jajuk/05_insubstantial_7.3.diff
>   https://github.com/fnatter/insubstantial-debian/blob/rdeps/rdeps/jajuk/MANIFEST.MF.diff

I just did:

https://github.com/jajuk-team/jajuk/issues/1994

[...]
>>
>> 1. Go ahead and package insubstantial as one source package that
>> provides the old binary packages from substance, trident,
>> liblaf-widget-java, etc. Maven poms should be provided as well. If you
>> also provide a patch to build with libasm4-java we could easily replace
>> the old dependencies for jajuk, bgfinancas, triplea and freeplane with
>> your new version and remove libasm2-java from Debian. (only
>> jasperreports would be an open issue but I would invest the time to fix
>> this package myself)
> 
> Agreed, I will work on providing poms. Two questions:
> 
> - can you think of a role model package for installing maven artifacts?
> 
> - Do I have to generate poms via gradle or shall/can I use+modify the
>   ones from maven.org?
>   (http://search.maven.org/#artifactdetails|com.github.insubstantial|flamingo|7.3|jar)

You can usually reuse the poms from maven.org. You can either use
javahelper + jh_maven_repo_helper

https://packages.qa.debian.org/libj/libjide-oss-java.html

or you can also depend on maven-debian-helper in addition to your normal
build system and install them too.

I think we figure that out as soon insubstantial is ported to
libasm4-java. Just ask on debian-java for a review.

Cheers,

Markus




Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: