s

sootkeeper

The use of static analysis allows developers to analyze the source code of a program. On one hand, developers get accurate data representing any issues with the program. On the other hand, static analysis programs can have lengthy execution times. This results in a large amount of developer idleness, waiting for their program to execute. A developer's debug cycles can be particularly time consuming, when tweaking their analyses. They then have to wait around for long periods of time to test their minor changes. In order to avoid this needless idle time, we have looked into modularizing a static analysis program in order to cut down on time wasted.
http://www.thewhitespace.de/projects/peaks/sootkeeper.html
Apache License, Version 2.0
Ben Hermann
cycles they periods test minor wait long amount consuming avoid time results when idleness programs execute static waiting code particularly representing program then issues this large other have data debug analysis execution hand wasted accurate order times allows lengthy with needless into modularizing developers around idle analyze tweaking source looked developer analyses down their changes
Files download
File Operation
sootkeeper-1.0.pom download
Apache Maven 
<dependency>
  <groupId>de.tu-darmstadt.stg</groupId>
  <artifactId>sootkeeper</artifactId>
  <version>1.0</version>
  <type>pom</type>
</dependency>
Gradle Groovy 
implementation 'de.tu-darmstadt.stg:sootkeeper:1.0'
Gradle Kotlin 
implementation("de.tu-darmstadt.stg:sootkeeper:1.0")
Scala SBT 
libraryDependencies += "de.tu-darmstadt.stg" % "sootkeeper" % "1.0"
Groovy Grape 
@Grapes(
  @Grab(group='de.tu-darmstadt.stg', module='sootkeeper', version='1.0')
)
Apache Ivy 
<dependency org="de.tu-darmstadt.stg" name="sootkeeper" rev="1.0" />
Leiningen 
[de.tu-darmstadt.stg/sootkeeper "1.0"]
Apache Buildr 
'de.tu-darmstadt.stg:sootkeeper:jar:1.0'
Dependencies

compile

|-- org.osgi:org.osgi.core:6.0.0