Re: Adding maven artifacts to library package

2015-10-31 Thread Markus Koschany
Hi, Am 31.10.2015 um 22:13 schrieb Felix Natter: > hello, > > I am working on the insubstantial (flamingo/substance/trident) package > for Debian: > https://github.com/fnatter/insubstantial-debian > > Is there a "role model" package for publishing maven artifacts? > > Shall I generate the POM

Adding maven artifacts to library package

2015-10-31 Thread Felix Natter
hello, I am working on the insubstantial (flamingo/substance/trident) package for Debian: https://github.com/fnatter/insubstantial-debian Is there a "role model" package for publishing maven artifacts? Shall I generate the POMs from the (gradle) build system or shall I adapt the poms from mave

Re: Packaging org.eclipse.jetty.alpn for Debian

2015-10-31 Thread Jonathan Yu
Removing alpn support impacts performance since an additional handshake is necessary at the application (http) level. Is it possible to instead patch the source to include the needed support class? It can then be removed when Java 9 becomes the default. On Sat, Oct 31, 2015, 12:38 Markus Koschany

Bug#803599: RM: libcommons-net1-java -- ROM; obsolete, superseded by libcommons-net-java

2015-10-31 Thread Markus Koschany
Package: ftp.debian.org Severity: normal Dear ftp team, please remove libcommons-net1-java from Debian. libcommons-net1-java is obsolete and was superseded by libcommons-net-java (>= 3). It has no reverse dependencies. There were no objections against this removal. [1] Thanks, Markus [1] htt

Re: Packaging org.eclipse.jetty.alpn for Debian

2015-10-31 Thread Markus Koschany
Am 31.10.2015 um 06:58 schrieb Emmanuel Bourg: > Le 30/10/2015 20:35, Markus Koschany a écrit : > >> What do you think? > > I don't mind having a single class package, it's fairly exceptional. An > alternative would be to ignore jetty-alpn and the related code (the > netty package does that alrea

Re: plans for eclipse luna in debian

2015-10-31 Thread Markus Koschany
Am 31.10.2015 um 15:46 schrieb Luca Vercelli: [...] >> Now I am wondering whether it would be ok to package 2.3.5 straight away, or >> does Eclipse strictly depend on 2.3.4? > > Well, I'm not sure of this, but I think 2.3.5 will be fine. > Also, w.r.t. the old package sat4j, it didn't put any link

Re: plans for eclipse luna in debian

2015-10-31 Thread Luca Vercelli
Il 31/10/2015 15:33, Michael Tautschnig ha scritto: > Hi, > > On Sat, Oct 31, 2015 at 13:23:41 +0100, Luca Vercelli wrote: >> I found out that eclipse depends on sat4j 2.3.4, and we have 2.3.3. >> There are some classes more in 2.3.4, so it is required. >> I have built 2.3.4 from source, it's quit

Re: plans for eclipse luna in debian

2015-10-31 Thread Michael Tautschnig
Hi, On Sat, Oct 31, 2015 at 13:23:41 +0100, Luca Vercelli wrote: > I found out that eclipse depends on sat4j 2.3.4, and we have 2.3.3. > There are some classes more in 2.3.4, so it is required. > I have built 2.3.4 from source, it's quite easy. I just had to write > some pom's myself. how can I sh

Re: plans for eclipse luna in debian

2015-10-31 Thread Luca Vercelli
I found out that eclipse depends on sat4j 2.3.4, and we have 2.3.3. There are some classes more in 2.3.4, so it is required. I have built 2.3.4 from source, it's quite easy. I just had to write some pom's myself. how can I share these? Thank you. Il 20/10/2015 19:06, Markus Koschany ha scritto: >