This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by Maven on behalf of the project.
| Document | Description |
|---|---|
| About | The 'Glue and Booster' project tries to be the glue between different (java) frameworks and will provide additional utilities to boost the power of the frameworks. It will provide easy to use facades which hide some of the complexity of the frameworks. Furthermore it will provide examples and ready to use templates with most of the configuration already done. This project has two main goals, two secondary goals and one meta-goal: 1.) Try to make the different frameworks "plug and playable". Take two frameworks, probably implement two simple interfaces and "Glue and Booster" will connect the frameworks. 2.) Provide implementations for additional features of some frameworks. These features may be missing simple factory methods that hide the complexity of the framework or real enhancements. Like a LogFactory for commons-logging and log4j that will provide FileAppender that write into different files (for example each transaction into one file) but are configured like the default FileAppender. This goal intents to present ready to use solutions. Maybe the code of the methods will only be some lines, but it will often take hours to find which lines to write. 3.) For the first goal the intention is to find suitable frameworks that contain the interfaces for the glue. Only when no fitting frameworks are found, then own interfaces are written. 4.) For some frameworks the glue interfaces will be implemented, too, so that these frameworks can be connected without effort. 5.) The meta-goal is, to write as few code as possible, but to put as much knowledge (and the time it needs to collect the knowlege) as possible into this framework. In this point this framework differs from other frameworks. It's goal is not to write a solution for one special problem or build a huge framework but trying to find tiny pieces of code that bridge the gap between frameworks or the gap between the requirements of the programmer and the functionality of the framework. |
| Continuous Integration | This is a link to the definitions of all continuous integration processes that builds and tests code on a frequent, regular basis. |
| Dependencies | This document lists the project's dependencies and provides information on each dependency. |
| Dependency Convergence | This document presents the convergence of dependency versions across the entire project, and its sub modules. |
| Dependency Management | This document lists the dependencies that are defined through dependencyManagement. |
| Issue Tracking | This is a link to the issue management system for this project. Issues (bugs, features, change requests) can be created and queried using this link. |
| Mailing Lists | This document provides subscription and archive information for this project's mailing lists. |
| Plugin Management | This document lists the plugins that are defined through pluginManagement. |
| Project License | This is a link to the definitions of project licenses. |
| Project Plugins | This document lists the build plugins and the report plugins used by this project. |
| Project Summary | This document lists other related information of this project |
| Project Team | This document provides information on the members of this project. These are the individuals who have contributed to the project in one form or another. |
| Source Repository | This is a link to the online source repository that can be viewed via a web browser. |