Bug#916361: ITP: apache-pulsar -- distributed pub-sub messaging platform
W dniu 13.12.2018, czw o godzinie 15∶28 +0000, użytkownik
Julien.Plissonneauduquene@ext.cdiscount.com napisał:
> Package: wnpp
> Severity: wishlist
> Owner: julien.plissonneauduquene@ext.cdiscount.com
> X-Debbugs-CC: debian-devel@lists.debian.org
>
> * Package name : apache-pulsar
> Version : 2.3.0-SNAPSHOT
> Upstream Author : Apache Pulsar contributors
> * URL : https://pulsar.apache.org/
> * License : Apache-2.0
> Programming Lang: Java
> Description : distributed pub-sub messaging platform
>
> I intend to maintain this package until it will be ready to hand
> over to Debian Java Maintainers.
>
> This is a large project and there are significant challenges:
> 1. getting the build to succeed with maven-debian-helper
> 2. fixing dependency requirements (downgrading or upgrading
> versions) for the dependencies that are already properly
> packaged; also fixing dependencies that are packaged but broken
> in some way
> 3. packaging dozens of dependencies that are not yet in Debian.
I do not know about Debian openjdk (I usually use Oracle JDK), but have
question.
Is it feasible to have common dependencies for all java libraries in
Debian. As Java developer I can say that it can be tricky to maintain.
It is no generic assumption in java world that API will not break
between two versions even not major update.
Maintaining one version of jar for whole Debian can be really messy.
What I usually do is to put application into /opt folder to make it
application manage it state on its own. Application servers for example
can have quite different classloaders behavior and it not necessary
make sens to do it different way.
>
--
Gaining from harming others is stricly prohibited.
Marek Mosiewicz
http://marekmosiewicz.pl
Reply to: