Re: Packaging Java Pathfinder

2015-11-14 Thread Marko Dimjašević
Hi again, On Thu, 2015-10-22 at 21:53 -0600, Marko Dimjašević wrote: > Hi all, > > Since earlier this year Java Pathfinder [1] (or JPF for short), an > implementation of JVM used for software verification, is free software > and available under the Apache 2.0 license. > > I would like to package

Re: Static code analysis tool in Debian

2015-11-14 Thread Marko Dimjašević
Hi Markus and Jonathan, On Sat, 2015-11-14 at 23:06 +0100, Markus Koschany wrote: > I think Jonathan has already listed the most common reasons why a > library hasn't been packaged yet. Thank you both for your replies! I'll take a look at tools you suggested and see if they suit (Soot :) ) my nee

Re: Static code analysis tool in Debian

2015-11-14 Thread Paul Wise
On Sun, Nov 15, 2015 at 5:49 AM, Jonathan Yu wrote: > Other great static code analysis tools (not just for doing call-tree I'm interested in adding general Java static analysis tools to check-all-the-things: https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git/ So far I have a

Re: Static code analysis tool in Debian

2015-11-14 Thread Markus Koschany
Am 14.11.2015 um 22:49 schrieb Jonathan Yu: > Hey Marko, > > In my experience, there are a few common reasons why libraries do not > end up in Debian: Hi, I think Jonathan has already listed the most common reasons why a library hasn't been packaged yet. [...] > Other great static code analysi

Re: Static code analysis tool in Debian

2015-11-14 Thread Jonathan Yu
Hey Marko, In my experience, there are a few common reasons why libraries do not end up in Debian: 1. Lack of time from maintainers: Debian is largely a volunteer effort, and as a result, sometimes things don't end up in Debian simply because people lack the time to package it. You can help here