s

sootkeeper-framework

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-framework-1.0.jar download
sootkeeper-framework-1.0.pom download
sootkeeper-framework-1.0-sources.jar download
Apache Maven 
<dependency>
  <groupId>de.tu-darmstadt.stg</groupId>
  <artifactId>sootkeeper-framework</artifactId>
  <version>1.0</version>
  <type>bundle</type>
</dependency>
Gradle Groovy 
implementation 'de.tu-darmstadt.stg:sootkeeper-framework:1.0'
Gradle Kotlin 
implementation("de.tu-darmstadt.stg:sootkeeper-framework:1.0")
Scala SBT 
libraryDependencies += "de.tu-darmstadt.stg" % "sootkeeper-framework" % "1.0"
Groovy Grape 
@Grapes(
  @Grab(group='de.tu-darmstadt.stg', module='sootkeeper-framework', version='1.0')
)
Apache Ivy 
<dependency org="de.tu-darmstadt.stg" name="sootkeeper-framework" rev="1.0" />
Leiningen 
[de.tu-darmstadt.stg/sootkeeper-framework "1.0"]
Apache Buildr 
'de.tu-darmstadt.stg:sootkeeper-framework:jar:1.0'
Dependencies 
<parent>
  <groupId>de.tu-darmstadt.stg</groupId>
  <artifactId>sootkeeper-analysiskeeper</artifactId>
  <version>1.0</version>
</parent>

compile

|-- com.google.guava:guava:20.0