j

jedi

Java's syntactic and library support for these components tends to cause the above concerns to be mixed with each other, with other concerns, and with low-level implementation details. This means that the code is cluttered, verbose and does not express intent very well. Jedi aims to repair this by providing a library of routines for filtering, iteration, conversion from one collection type to another, first order logic functions, etc. It makes extensive use of higher order functions and closures (also known as 'blocks' or 'lambdas' that can be implemented manually or by annotations.
http://jedi.codehaus.org/
MIT License
Lance Walton Channing Walton
cause tends cluttered filtering higher type concerns iteration level verbose repair aims these support means manually providing code lambdas logic jedi that each known components this does other conversion closures well from collection express routines another extensive details order syntactic above mixed functions with makes implemented blocks intent implementation library java annotations first also very
Files download
File Operation
jedi-3.0.5.pom download
Apache Maven 
<dependency>
  <groupId>org.codehaus.jedi</groupId>
  <artifactId>jedi</artifactId>
  <version>3.0.5</version>
  <type>pom</type>
</dependency>
Gradle Groovy 
implementation 'org.codehaus.jedi:jedi:3.0.5'
Gradle Kotlin 
implementation("org.codehaus.jedi:jedi:3.0.5")
Scala SBT 
libraryDependencies += "org.codehaus.jedi" % "jedi" % "3.0.5"
Groovy Grape 
@Grapes(
  @Grab(group='org.codehaus.jedi', module='jedi', version='3.0.5')
)
Apache Ivy 
<dependency org="org.codehaus.jedi" name="jedi" rev="3.0.5" />
Leiningen 
[org.codehaus.jedi/jedi "3.0.5"]
Apache Buildr 
'org.codehaus.jedi:jedi:jar:3.0.5'
Dependencies 
<parent>
  <groupId>org.codehaus</groupId>
  <artifactId>codehaus-parent</artifactId>
  <version>3</version>
</parent>
The project has no third-party dependencies