The application is now implemented as a "model 1" application using JSPs and scriptlets. This project is migrating the application to [Struts 2|http://struts.apache.org/2.x/index.html]. The source code is available at [Struts SourceForge|http://svn.sourceforge.net/viewcvs.cgi/struts/SportsForge/v2]. To checkout the source, use the [Subversion|http://subversion.tigris.org/] command

To build the Struts and SportsForge source, install [Maven 2|http://maven.apache.org/]. Then, change to the Struts folder and run {{mvn install}}. When that process completes, change to the SportsForge folder and run {{mvn install}} again.

If you are using IDEA, you can run {{mvn idea:idea}} to generate the IDEA projects. For Eclipse, you can run {{mvn eclipse:eclipse}}.{tip}

The project shares with Apache Struts and the ASF common values regarding collaborative, community-based open source development. Volunteers are invited to [subscribe to the mailing list|https://lists.sourceforge.net/lists/listinfo/struts-sportsforge-dev] to get started.

h2. Documentation

* [Requirements]

* [Use Cases]

* [Data Model]

h2. Resources

| [Portal|http://opensource.atlassian.com/confluence/oss/display/sportsforge/Home] | The project portal describes the application to both users and developers. (_You are here._ ) |

| [Repository|http://svn.sourceforge.net/viewcvs.cgi/struts/SportsForge2] | The repository contains a working copy of project materials, including source code and the portal. |

| [Mailing List|https://lists.sourceforge.net/lists/listinfo/struts-sportsforge-dev] | The mailing list is the nexus of team communication. All development decisions should be made on the list, even if by summary of any meetings, chats, or telephone conferences. Ideally, all changes to the Portal, Repository, or Issue Tracker, should be logged to the list, or [List Archive|http://opensource.atlassian.com/confluence/oss/spaces/viewmailarchive.action?key=sportsforge]. |

h3. External Resources

* [SportsForge: A Working Example|http://jroller.com/page/TedHusted?entry=sportsforge]

h2. Next Steps

|| (/) | Setup PRIM infrastructure |

|| (on) | Define [requirements] and [use cases]. |

|| (on) | Implement a use case as a working example and starting point. |

|| (off) | Prioritize the use cases in terms of a series of interations in which we implement the use cases. Each iteration should produce an application that does some useful work. |