Page History

...

Getting Started

Please read https://git-wip-usgitbox.apache.org/ first.

Windows users (especialy EGit users) should probably set the core.autocrlf config setting to false so that local diffs won't highlight line ending differences.

...

Clone Tapestry from the Git repo:

• Command-line git users:

  Non Committers:

  git clone

  http://git-wip-us.apache.org/repos/asf/tapestry-5.git

  Committers:

   

  git clone

  https://

  git-wip-us

  gitbox.apache.org/repos/asf/tapestry-5.git

   

  
  

• Eclipse EGit users:
  • Switch to Git perspective; then copy one of the URLs URL above into paste buffer
  • Right-click > Paste repository path or URI. This will bring up the Clone Git Repository dialog.
  • Committers: make sure Protocol is https, and enter your Apache commiter LDAP user name & password
  • click Next.
  • Select the branches you're interested in (e.g 5.3 and master), click Next
  • Select Directory to where you want the project source code (e.g. ~/git/tapestry-5 or %HOME%\git\tapestry-5)
  • Select whichever "Initial Branch" you're interested in (e.g. master)
  • Set "Remote name" to "origin" (the default)
  • VERY IMPORTANT: uncheck the "Import all existing projects" checkbox (we'll do this using Gradle, below)
  • Click Finish. (Be patient; the clone operation might take a few minutes.)

...

The integration test apps are:

• activationctx – used by tapestry-core integration tests
• activationctx2 – used by tapestry-core integration tests
• app0 – used 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:

...

Solution: Use the gradle wrapper (./gradlew build), not plain "gradle". 

...

Problem 2: Under Linux I get java.io.FileNotFoundException saying "Too many open files"

...