Explore >> Select a destination
|
You are here 
|
dagger.dev | ||
| | | | |
msfjarvis.dev
|
|
| | | | | Dagger is universally intimidating to beginners and I want to change it. | |
| | | | |
ryanharter.com
|
|
| | | | | I recently gave a presentation about how Dagger works under the hood, and I was once again struck by the elegance of the javax.inject.Provider interface. The interface is so simple it almost seems useless, but it's also incredibly flexible, and forms the basis of much of the code generated by Dagger. Like many dependency injection frameworks for JVM languages, Dagger uses and builds on the standard set of annotations for injectable classes defined in JSR-330 and provided in the javax. | |
| | | | |
daniel-siepmann.de
|
|
| | | | | Explanation of how Dependency Injection works for TYPO3 Extbase (prior TYPO3 CMS v10). | |
| | | | |
sookocheff.com
|
|
| | | I've been experimenting with the Google Cloud Dataflow Java SDK for running managed data processing pipelines. One of the first tasks is getting a build environment up and running. For this I chose Gradle. We start by declaring this a java application and listing the configuration variables that declare the source compatibility level (which for now must be 1.7) and the main class to be executed by the run task to be defined later. | ||
