Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Command-line users:
    • ./gradlew runTestApp1
  • Eclipse users:
    • Use the run-jetty-run plugin in Eclipse, with the context directory selected from among the test context directories. For example, in the tapestry-core module, right click on the /src/test/app1 (or app2, etc) folder, and select Run As > Run Jetty, then open your browser to http://localhost:8080/tapestry-core

The "app1" app (the runTestApp1 tasks, above) is the one used by most of the integration tests. There are also app0, app2, app3, app4 and appfolder apps that can be run the same way.integration test apps are:

  • 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

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:

...