Welcome to the Turbine Wiki
Welcome to the Turbine Project Wiki pages. Here you'll find documentation, FAQs, and other items for Turbine and all its subprojects.
You are invited to contribute to these pages. Due to excessive spamming, we were forced to limit access to the wiki. So if you want to contribute, just contact us with the name of your wiki account and we will be happy to give access to you.
Turbine-Build and Fulcrum-Build Git Multi-module repositories provide a Jenkinsfile.
Using this together with .asf.yaml (INFRA) in Apache CI (Jenkins) enables an (semi-)automatic (form-parameter-based) Site Build of each project. That is it allows a site build to be triggered manually in Jenkins. Each project has to provide a branch asf-site.
- turbine-build Jenkinsfile → Turbine-Build-Site Job (Apache CI Jenkins)
- turbine-fulcrum-build Jenkinsfile → Turbine-Fulcrum-build-Site Pipeline Job (Apache CI Jenkins )
After Login you see "Build With Parameters". Select the parameters carefully (most repos have master, only core has currently trunk) and start site building!
N.B. In Fulcrum Pipeline staging is not the staging site, but the kind of site building (multi or single module).
Read README_TECHNICAL_SITE_STRUCTURE.md (github) to find more details about it! Jenkinsfile are already available.
By default Turbine core .asf.yaml is configured like this: The subdir is the currently active development subdir, e.g. Turbine-5-2 site (N.B. avoid dots)
publish: whoami: asf-site # subdir: turbine # subdir: turbine/turbine-5-1 subdir: turbine/development/turbine-5-2
Site targets by default point to the current published site.
publish: whoami: asf-site subdir: fulcrum/fulcrum-cache
Find more info about how to do it Publishing a Release and the README.md (Github) section publishing-workflow.
Turbine 2/3, META, Torque, JCS, Stratum, Maven
- Turbine 3 - Version 3 of the Turbine project. Development of version 3 has halted - it was an experimental version, the best bits of which have now been ported back to version 2.
- Turbine 2 - Version 2 of the Turbine project. The latest release version of this branch is 2.3.3. The release version has proved to have production quality.
- TDK - The Turbine Development Kit (TDK) is a package that bundles a copy of Turbine, Tomcat, jar files, documentation and other utilities in order to help you get started with Turbine as quickly as possible. The installation steps outlined below should have you up and running quickly. The [http://turbine.apache.org/tdk/ is no longer being developed, as well as META. You should now checkout Turbine Archetype Blog.
- META - The Maven Environment for Turbine Application (M.E.T.A.) helped you to write Turbine applications. You should now checkout the Turbine Archetype Blog.
- Torque Wiki - Torque is a persistence layer which generates all the database resources required by your application and includes a runtime environment to run the generated classes. Torque was developed as part of the Turbine Framework. It is now decoupled and can be used by itself. Torque started life as a Turbine sub-project, but is no longer part of Turbine - it now lives in Apache DB.
- JCS is a distributed caching system written in java for server-side java applications. It came into the ASF as a Turbine sub-project, it is now a direct sub-project of Apache Commons JCS.
- Stratum another retired sub-project.
- Maven started life as a Turbine sub-project!
- Board Reports of Apache Turbine Project.
- SubProjectReports - this was back when Turbine was part of Apache Jakarta.
- ApacheCon07EU - who is going, thoughts on what might be achieved.
- TLPTurbine - the proposal for Turbine to become a Top Level Project (TLP) of the ASF. This went to the ASF board on May 15, 2007 and was passed, thus making Turbine a TLP of the ASF.