This document provides an overview of the various documents and links that are part of this project's general information:
- Community Roles and Processes
- Project Team
- Mailing Lists
- Issue Tracking
- Source Repository
- Continuous Integration
- Project License
These are the mailing lists that have been established for this project. For each list, there is a subscribe, unsubscribe, and an archive link.
|Sling Users List||Subscribe||Unsubscribe||users at sling.apache.org||mail-archives.apache.org||www.mail-archive.com MarkMail Nabble|
|Sling Developers List||Subscribe||Unsubscribe||dev at sling.apache.org||mail-archives.apache.org||www.mail-archive.com MarkMail Nabble|
|Sling Source Control List||Subscribe||Unsubscribe||mail-archives.apache.org||www.mail-archive.com MarkMail|
This project uses JIRA a J2EE-based, issue tracking and project management application. Issues, bugs, and feature requests should be submitted to the following issue tracking system for this project.
The issue tracker can be found at http://issues.apache.org/jira/browse/SLING
This project uses Subversion to manage its source code. Instructions on Subversion use can be found at http://svnbook.red-bean.com/.
The following is a link to the online source repository.
The source can be checked out anonymously from SVN with this command:
Everyone can access the Subversion repository via HTTPS, but Committers must checkout the Subversion repository via HTTPS.
To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password)
For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via the developer connection:
The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)
There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.
Example : Edit the 'servers' file and add something like :
Sling builds run automatically on the ASF's Jenkins build server, triggered by SVN changes and daily.
See SLING-920 for Hudson configuration information.