Page History

...

The integration test apps are:

• activationctx – used by tapestry-core integration tests
• activationctx2 – used by tapestry-core integration tests
• app0 – used only by the tapestry-hibernate integration tests
• app1 – used by most of the tapestry-core integration tests
• app2 – used by tapestry-core integration tests (HTTPS)
  app3 – used by tapestry-core integration tests
• app4 – used by tapestry-core integration tests
• app5 – used by tapestry-core integration tests
• appfolder  – used by tapestry-core integration tests
• cluster – used by tapestry-core integration tests
• linktrans – used by tapestry-core integration tests
• symbolparam – used by tapestry-core integration tests
• (...and a few others not yet documented, and without Gradle tasks yet. Search for web.xml files in the Tapestry source.)

Making Code Changes

Once you have cloned or pulled the latest changes to your local Git repository, you can start working on it. Whenever you make some changes to the codebase, it's good to have a related issue filed in JIRA and to use a similarly named branch in your local Git repository. For example, to create a branch for an issue with the key TAP5-123:

...